owned this note
owned this note
Published
Linked with GitHub
# Use Case Testing form - UC1
**Reviewer**: Marisa
**OS (including version)**: MacOS 10.15.7
**Browser (including version)**: Firefox 85.0.2
**Use case**: [use case 1](https://use-cases.nih-cfde.org/uc-0001/)
**Review type**: manual
**Role groups**: Groups entry is blank
# Use Case Test
<details><summary>Instructions</summary>
<p>
I would like each use case checked by at least two people. Preferably with a mix of browsers and OS, so that we have a better chance of spotting potential bugs.
1. Choose a use case that you will validate
2. Copy the text from the next comment into a new document
3. Follow the use case, filling out the document as you go
4. If you encounter one of the Quick Tests, check that it is right and check it off. If you don't encounter it as part of your use case, leave it blank
5. When you are done with your use case, post your filled form as a comment in this thread
I recommend starting by looking at the Quick Tests section and seeing which ones will be part of your use case so you can check them as you go instead of backtracking at the end
</p>
</details>
## Use Case Description
**1. Evaluate the description.**
- Does this description make sense?
- yes (though actually following the search steps is more difficult)
- Does it sound like a useful thing to do?
- yes
- Are there any corrections that should be made (spelling, grammar, etc)?
- after trying the use case, needs to be fixed so it all works - details below!
**2. Try to complete the steps as they are described for the persona in the use case.**
<details><summary>Instructions</summary>
<p>
For each step record:
- the specific action you took, for e.g. I clicked on 'leg' in the 'anatomy' filter at [this web address]()
- Whether that action was possible/worked
- Whether the *results* of that action are as described
- and if they are not as described, how they differ
- Any other comments you have, or things you were surprised about. Be specific!
Copy the lines below as many times as needed for your use case
</p>
</details>
Action: Go to CFDE interface - https://app.nih-cfde.org/ - and click "Log on"
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
![](https://i.imgur.com/Fm9RJaQ.png)
Action: search for brain data
- [ ] Worked
- [ ] Results as expected
- If not, why not: I'm on the home page and not sure where to enter search terms
- Other Comments:
Action: I'll keep going so I can test the rest of the use case. Assume we add a step that says 'Go to Collections and search for brain data' in the Anatomy Refine search box
- [x] Worked
- [ ] Results as expected
- If not, why not: I can see in the Anatomy Refine box that the terms have narrowed down to those related to the brain. It's not that obvious looking at the table view though that the search results are related to brain.
- Other Comments
- the user has to know where in the portal a search of "brain" works (i.e., there are no results unless I search from Collections)
- do users search for terms in the top search box or in the Refine search box? --> I get more results by searching for "brain" in the Anatomy Refine search box
![](https://i.imgur.com/qxBzCRm.png)
Action: filter results to those studies that used RNASeq --> by checking box next to "RNA sequence" in Data Type Refine search section
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
![](https://i.imgur.com/pryhkRS.png)
Action: Search for 'FCD' or 'Focal Cortical Dysplasia'
- [ ] Worked
- [ ] Results as expected
- If not, why not: Neither search terms have results (don't think disease metadata is in the portal yet?). Since these search terms don't bring up any results, "KidsFirst additional cohorts" are *not* identified
- Other Comments
Action: initial search with cerebral cortex identifies GTEx and HuBMAP
- [ ] Worked
- [ ] Results as expected
- If not, why not: when I search for "cerebral cortex", the closest result is "dorsolateral prefrontal cortex". The only dataset is GTEx Release V8. Nothing from HuBMAP
- Other Comments
![](https://i.imgur.com/os0A0rE.png)
Action: using links in these search results, access Program page for dataset and request access to ones that fit their needs. --> I clicked "View Details" > Export > search results (csv)
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
- It's hard to know what to click on to get the manifest (maybe we need an obvious button that says "Get metadata!"). The resulting csv file has a few links, not sure which of them to use to get the dataset. The persistent ID seems like a good one: https://identifiers.org/dbgap:phs000424.v8.p2. That takes me to the dbGaP page.
- I know this functionality is still in progress. At any rate, knowing where to click and what to do with the manifest are non-intuitive.
<!--
Action:
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments -->
## Tasks for this use case:
1. Based on the description you walked through, does this list of tasks make sense? If not, why not? Are there missing tasks? Unused tasks? Task descriptions that don't quite match the workflow? Be specific both about which tasks and their specific problems.
Most of the tasks are general enough to make sense, these few don't quite work/match:
- `t-0019: Search/filter data sets by project`
- I was able to search for brain and RNA seq terms from Collections (steps detailed above - didn't realize I should look in Projects)
- However, I can also search for them from Projects ("brain" from Anatomy Refine; "RNA-seq assay" & "RNA sequencing assay" from Assay type Refine), but the results look different. I get results from LINCS, 4DN, KF, HMP, but *not* GTEx!
- `t-0005: Search/filter data by assay type terms` - this works by searching for "RNA-seq assay", but it also works to refine search with "RNA sequence" in data type. Is one better than the other?
- this use case has disease-related search terms, a) they're not on the portal yet? b) if they'll be added to the portal we need another task to `Search/filter data by disease type terms`
2. Check whether each general task works, regardless of whether the specific instance described in the description works.
<details><summary>Instructions</summary>
<p>
For each task record:
- the specific action you took, for e.g. I clicked on 'leg' in the 'anatomy' filter at [this web address]()
- note that tasks are generally broader than the description, so you likely will need to do more than one action to test it
- Whether that action was possible/worked, i.e. was it technically possible to do?
- Whether the *results* of that action are what you expect, i.e. did it 'work' in the way a user would want
- and if they are not as described, how they differ
Copy the lines below as many times as needed for your use case
</p>
</details>
Action: t-0001: Access CFDE interface --> I went to portal website.
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0002: Use link within the CFDE interface to access original data source --> clicked on a file and found its persistent ID, which directed me to the Program website portal (in this case 4DN's page)
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0019: Search/filter data sets by project ---> "Browse all data" > "Project" > used Refine search boxes
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0004: Search within dataset descriptions
- [x] Worked
- [x] Results as expected
- If not, why not: this is quite a general task, was able to use free text searches
- Other Comments
Action: t-0005: Search/filter data by assay type terms --> Searched for "RNA" > checked boxes by "RNA-seq assay" and "RNA sequencing assay"
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0006: Search/filter data sets by anatomic terms --> searched "brain" and "cerebral cortex"
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
- I get multiple brain-related anatomy terms
Action: t-0010: Visualize a table of all datasets that match query
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0003: Export a file of results --> clicked "Export" > "search results (csv)"
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
<!-- Action:
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments -->
## Requirements for this use case:
1. Based on the description you walked through and it's tasks, does this list of requirements make sense? If not, why not? Are there things you needed but are not listed as requirements? Unused requirements? Requirement descriptions that don't quite match the workflow? Be specific both about which requirements and their specific problems.
- `r-00003: The interface will support the selection of an Uberon term of interest`
- I didn't know offhand what the Uberon ID was for brain terms. So while this would work for finding a specific brain anatomy term, it's not necessarily a requirement
- `r-00012: The interface will render tables and plots to display filtered data`
- I don't see any plots associated with my filtered data
2. Check whether each requirement works, if possible, regardless of whether the specific instance described in the description works.
<details><summary>Instructions</summary>
<p>
For each requirement record:
- the specific action you took, for e.g. I clicked on 'leg' in the 'anatomy' filter at [this web address]()
- note that requirements are very broad, so you may need to do more than one action to test it
- if you can't find a way to test the requirement, record that and why
- Whether that action was possible/worked, i.e. was it technically possible to do?
- Whether the *results* of that action are what you expect, i.e. did it 'work' in the way a user would want
- and if they are not as described, how they differ
</p>
</details>
Action: r-00001: The interface will support GUI web access to end users
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: r-00002: The interface will support user authentication --> clicked "Log in"
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: search of anatomy terms involves these requirements -
- r-00003: The interface will support the selection of an Uberon term of interest
- r-00004: The C2M2 model will support information relating anatomy terms to CF programs
- r-00005: The catalog will store information relating anatomy terms to CF programs
- [ ] Was not testable
- [x] Worked
- [x] Results as expected - was able to use the anatomy search, so the model/interface/catalog supports it
- If not, why not:
- Other Comments
- caveat: can search for anatomy from certain parts of the portal (Collections, Projects)
- I did not need to use Uberon terms in the Refine search Anatomy box
Action: search of assay type terms involves these reqs -
- r-00006: The interface will support the selection of an assay type term of interest
- r-00007: The C2M2 model will support information relating assay types to CF programs
- r-00008: The catalog will store information relating assay types to CF programs
- [ ] Was not testable
- [x] Worked
- [x] Results as expected - was able to use assay type search, so the model/interface/catalog supports it
- If not, why not:
- Other Comments
Action: r-00009: The interface will support free text search of results --> searched for "brain", "RNA", "cerebral cortex"
- [ ] Was not testable
- [x] Worked
- [ ] Results as expected
- If not, why not: the search seemed to work better in the Refine search box vs. the top search bar. When searching from the top search box, it was not very clear whether the filter was working
- Other Comments
Action: search of projects involves these reqs -
- r-00010: The catalog will store information relating projects to CF programs
- r-00011: The C2M2 model will support information relating projects to CF programs
- [ ] Was not testable
- [x] Worked
- [x] Results as expected - was able to search projects, so the model/catalog support it
- If not, why not:
- Other Comments
Action: r-00012: The interface will render tables and plots to display filtered data
- [ ] Was not testable
- [ ] Worked - yes for tables, don't know how to see plots of filtered data
- [ ] Results as expected
- If not, why not:
- Other Comments
Action: finding original data sources involves these reqs -
- r-00013: The interface will support links to original data sources within the results
- r-00032: The C2M2 model will support links to original data sources
- r-00033: The catalog will support links to original data sources
- [ ] Was not testable
- [x] Worked
- [x] Results as expected - was able to use persistent ID links. Checked for GTEx (to dbGaP) and 4DN (to 4DN portal)
- If not, why not:
- Other Comments
Action: r-00014: The interface will support end user download of tables and figures in common formats
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
- tables in csv, images from the dashboard as e.g., png
<!-- Action:
- [ ] Was not testable
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments -->
# Overall
What difficulties did you encounter while completing your use case?
- where to click - there are at least 2 ways to do a similar search, but got different results
- knowing what to do with the exported csv file is not intuitive
- there are no matches for "FCD" or "Focal Cortical Dysplasia", made following the exact use case hard
- searching by anatomy is not straight-forward - sometimes resulted in "Bad Request: The result set cannot be retrieved" when searching for "brain" or a more specific brain anatomy term like "cerebral cortex".
Did you see any spelling, grammar or similar mistakes on any resource you visited in completing your use case?
- no
What other comments or questions do you have about your use case?
- this one needs to be updated so it doesn't have disease type terms until those are available on the portal OR marked as something we'd like the portal to do but doesn't yet
What other comments or questions do you have about any of the resources you visited?
What feedback do you have about this form/testing process?
- feels a bit repetitive. it would be helpful for testing/using use cases as a guide if tasks were listed in order of operation with associated requirements on the UCL.
## more details for "Bad Request" error
- go to https://app-staging.nih-cfde.org
- not logged in
- click "SEARCH ALL COLLECTIONS" button from home page
- type "brain" in the Anatomy Refine search side bar
![](https://i.imgur.com/Y2nHUqL.jpg)
- click "Show More", select box by "brain", click "Submit"
![](https://i.imgur.com/K8oDPMu.jpg)
# Quick Tests
Complete test if it is encountered as part of your use case.
- If test works/work is complete check the box.
- If you don't encounter the test during your use case, leave it blank
- If test does not work/work is not complete
Home page
- [ ] Download button style now matches wireframe
- [ ] chart in upper right corner reflects data
- [ ] Color Palette is updated
Dashboard
- [ ] "Select Data view" box present to show which dashboard graphs are available
- [ ] Download button style now matches wireframe
- [ ] Timestamp for data missing
DCC Review
- [ ] Numbers have links
- [ ] Scroll bar in Data Review table
Registry
- [ ] [Spelling correct](https://github.com/nih-cfde/cfde-deriva/issues/131)
Navbar
- [ ] Bolded option in navbar when page is selected
- [ ] Log out button styles
- [ ] Locks next to Dashboard and Data Review links missing
- [ ] Color Palette
[Link to QA screens for reference](https://drive.google.com/file/d/11-SVyGzTsKy5Ke8o6s_lFE6LCF_BrJ2a/view)