owned this note
owned this note
Published
Linked with GitHub
# Use Case Testing form - UC2
**Reviewer**: Marisa
**OS (including version)**: MacOS 10.15.7
**Browser (including version)**: Firefox 85.0.2
**Use case**: [use case 2](https://use-cases.nih-cfde.org/uc-0002/)
**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?
- the goal makes sense, guessing how to do the tasks
- Does it sound like a useful thing to do?
- yes!
- Are there any corrections that should be made (spelling, grammar, etc)?
**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
Action: get a matrix of Uberon tissue terms by DCC --> clicked on the summary chart from home page. Stack by "Anatomy", X-axis is "CF Program", Y-axis is "File count". Export chart as a CSV file.
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: get similar tables showing Species by Program --> clicked on the summary chart from home page. Stack by "Species", X-axis is "CF Program", Y-axis is "File count". Export chart as a CSV file.
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: get similar tables showing Assay Types by Program --> clicked on the summary chart from home page. Stack by "Assay", X-axis is "CF Program", Y-axis is "File count". Export chart as a CSV file.
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: re-plot the data in almost any piece of plotting software, or look at the results in Excel --> made stacked bar plots in Excel from the csv matrices
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: Jon downloads the underlying data to add to a report they are making about Common Fund assets --> can download data
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
<!-- 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.
- `t-0017: Authenticated access to the CFDE interface`
- The way I got the tables, it wasn't necessary to be logged in to the portal.
- The rest of the tasks are general enough to make sense for this use case, although it might not be obvious to get these matrices by clicking on the bar plot menus vs. searching the collections, etc.
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-0017: Authenticated access to the CFDE interface --> clicked "Log in"
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0003: Export a file of results
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
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-0011: Search/filter CF Programs by anatomic terms
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0012: Search/filter CF Programs by assay type terms
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: t-0020: Search/filter CF Programs by species terms
- [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.
see comments below! the 2 requirements I didn't really need/notice needing for this use case were:
- `r-00002: The interface will support user authentication`
- `r-00037: The interface will support linking an SSO identity to an organization profile`
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
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: related to anatomy search
- 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
- If not, why not:
- Other Comments
- these reqs work, but Uberon search isn't used AFAICT for this use case. I guess it would be an underlying req in order for any of the anatomy terms to show up in the summary bar plot though?
Action: related to assay type search
- 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
- If not, why not:
- Other Comments
Action: r-00012: The interface will render tables and plots to display filtered data
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- 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
Action: related to species search
- r-00015: The interface will support the selection of a species term of interest
- r-00016: The C2M2 model will support information relating species terms to CF programs
- r-00017: The catalog will store information relating species terms to CF programs
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
Action: r-00037: The interface will support linking an SSO identity to an organization profile
- [ ] Was not testable
- [x] Worked
- [x] Results as expected
- If not, why not:
- Other Comments
<!-- 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?
- i guessed where to find matrices for program x search term, not sure if there's a better way on the portal to get these results
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?
- could use a bit more direction on where to get these matrix tables
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?
# 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
- [x] Download button style now matches wireframe
- [ ] chart in upper right corner reflects data
- [x] 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
- [x] Color Palette
[Link to QA screens for reference](https://drive.google.com/file/d/11-SVyGzTsKy5Ke8o6s_lFE6LCF_BrJ2a/view)