Overview
Test case for normal use of the REST content service concept retrieval methods.
Procedure 1: Get concepts
- Get concepts for terminology/version
- getConcepts("138875005",...) for SNOMEDCT
- TEST: Returns one concept, terminology id 138875005
- Get concept for user based on previous call
- Authenticate user who last modified concept 138875005
- getConceptForUser() with new auth token
- TEST: Returns one concept, terminology id 138875005, last modified by appropriate user
- TODO: Move this routine to ContentChangeService
- Get single concept
- getSingleConcept("138875005", ...) for SNOMEDCT
- TEST: Returns one concept, terminology id 138875005
- Get concept by id
- getConcept(concept.getId(), ...)
- TEST: Returns one concept, terminology id 138875005
Procedure 2: Find concepts
- For all tests, execute findConceptsForQuery("ossification", ...) for SNOMEDCT
- Raw results – No pfs parameter
- TEST: 14 results
- Sorted results – Pfs parameter with sortField defaultPreferredName
- TEST: 14 results, sorted alphabetically
- Paged, sorted results, first page – Pfs parameter with max results 5 and sortField defaultPreferredName
- TEST: 5 results, matching first 5 results from previous test
- Paged, sorted results, second page – Pfs parameter with startIndex 6, max results 5 and sortField defaultPreferredName
- TEST: 5 results, matching second set of 5 results from previous test
Expected Runtime
- < 1 sec
Notes
- n/a