owned this note
owned this note
Published
Linked with GitHub
# uc-0007: Use Case Testing form
**Reviewer**: Saranya Canchi
**OS (including version)**: macOS Big Sur v11.2.1
**Browser (including version)**: Chrome v88.0.4324
**Use case**: [uc-0007](https://use-cases.nih-cfde.org/uc-0007/)
**Review type**: <manual or Selenium> manual
- I tried selenium IDE testing route but it kept running into timeout errors and/or Undetermined errors
**Review Date**: 02/17/2021
**Role groups**: NA (did not login)
# 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. If it doesn't work, add some text explaining the problem
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. I would clarify that after typing “stem cell neu” they use the “Part of Collection” to refine the search and then export --> you get 2 results.
The way it is current written one could interpret it as type stem cell neu and export --> you get 36 matching results.
- 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: **[t-0001](https://use-cases.nih-cfde.org/t-0001/)** - accessed staging portal website: https://app-staging.nih-cfde.org and clicked on "SEARCH ALL COLLECTIONS" button.
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
---
Action: Typed ipsc in the search bar and got 19 matching sets
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
- need a specific task that is about using the serach bar across all columns of a given facted page
---
Action: Clicked "Part of Collection" filter and selected the all the sets that applied. Clicked "Submit". The list updates to show only 9 matching results
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
- need a specific task that is about search/filter data sets by part of collection
---
Action: Clicked "Export" and subsequently "Search results (CSV)" to obtain the mainfest locally
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
---
Action: Clicked "Clear all filters" and typed "stem cell neu" in the search bar. Got 36 matching results
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
- need a specific task that is about using the serach bar across all columns of a given facted page
---
Action: Clicked "Part of Collection" filter and selected the all the sets that applied. Clicked "Submit". The list updates to show only 2 matching results.
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
- need a specific task that is about search/filter data sets by part of collection
---
Action: Clicked "Export" and subsequently "Search results (CSV)" to obtain the mainfest locally
- [x] 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.
Task not used in this usecase:
- t-0018
- t-0006
- t-0005
- t-0019
Missing tasks:
- need a specific task that is about using the serach bar across all columns of a given facted page
- need a specific task that is about search/filter data sets by part of collection
2. **OPTIONAL (if not already addressed above):**
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:
- [ ] Worked
- [ ] 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.
Requirements used in this usecase:
- r-00001
- r-00014
All the rest of the requirements in this list are not directly used in this usecase. Similar to tasks, requirments missing are those related to search across all columns and using part of collection.
The requirement r-00002 maybe unneccesary since this use case can be completed without loggin into the portal.
2. **OPTIONAL (if not already addressed above):**
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:
- [ ] Was not testable
- [ ] Worked
- [ ] 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?
Did you see any spelling, grammar or similar mistakes on any resource you visited in completing your use case?
What other comments or questions do you have about your use case?
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, note the issue. Be specific!
[Link to QA screens for reference](https://drive.google.com/file/d/11-SVyGzTsKy5Ke8o6s_lFE6LCF_BrJ2a/view)
Home page
- [x] Download button style now matches wireframe
- [x] 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
- The Data Review tab is in a different color and there is no space between the lock icon and hearder name
- [x] Color Palette