# Use Case 1 Researcher Browser and Filter - Jose

# Use Case Testing form

**Reviewer**: Jose Sanchez
**OS (including version)**: Windows 10 (1909)
**Browser (including version)**: Google Chrome
**Use case**: [use case 1](https://use-cases.nih-cfde.org/uc-0001/)
**Review type**: Selenium
**Role groups**: No Group <either not logged in or exactly record all group names> <click your name in the top right corner and view your profile to find group names>

# 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. It has a clear goal "build a summarized metadata and summary statistics from each RNA-Seq dataset in the Common Fund that relates to Focal Cortical Dysplasia.
- Does it sound like a useful thing to do?
- Yes, completing this task will bring up useful metadata and links to the DCC portals that will have that related datasets and infromation. If a researcher is interested in any datasets related to Focal Cortical Dysplasia, this would be helpful to find all resources and links to relevant DCC portals that contain that information.
- Are there any corrections that should be made (spelling, grammar, etc)?
- the word "addtional" (located in "Searching with FCD identifies KidsFirst addtional cohorts that included this clinical finding." )
- 

**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: From the Main page https://app-staging.nih-cfde.org/ , clicked the log-in button and sign in with a generic gmail account.
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments

Action: Clicked on "Search All Collections"
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments:
It would be helpful for the use case description to describe what button I should press or what search bar should I type in to begin my "brain" search. For now, I assumed that I am supposed to click in "Search All Collections" to begin looking for datasets.

Action: Under Data Type in the Refine Search Bar, I checkmarked the RNA Sequence box.
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments
- After checking the box, I receive one collection and it is related to GTEx. It would be helpful for some kind of indication that a single row represents a group of files.

Action: I clicked on "View Details" on the GTEx result
- [x] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments:
It would be helpful to indicate on the collections page, that each row represents a group of files.

Action: I clicked on Explore to search by Subject:
- [ ] Worked
- [ ] Results as expected
- If not, why not: I was expecting to see a list of anatomies to help me find something on the brain. But none of the columns had info on anatomies
- Other Comments

Action: On the collections page, I clicked on Contained Biosample because it included a list of anatomies that I could use to find metadata with information on anything the portal has on the brain. Afterward I clicked on Explore to filter and typed brain to find any files with metadata on the Brain.
- [ ] Worked
- [x] Results as expected
- If not, why not:
- Other Comments:
- Currently, there is no metadata on the brain.

Action: Since I don't have info on the brain, I decided to pick local id GTEX-14PJM-2426 which has metadata info on an ovary. I clicked on ovary checkbox in the anatomy "Refine Search" section.
- [x] Worked
- [ ] Results as expected
- If not, why not: It is great that it filters data based on what you select in the Refine Search Check boxes, but I did not find ovary files if I use the "search all columns" search bar.

> [name=Amanda Charbonneau]submitted ticket
- Other Comments
- Image: 

Action: After I check the ovaries and RNA Sequence boxes, I exported a .csv file with a table for ovaries.
- [x] Worked
- [ ] Results as expected
-
- Other Comments
- It would be great to know what RID, RCT, RMT, RCB, RMB are in the exported .csv file in the column name. You can figure out a few of them based on the inputs.

> [name=Amanda Charbonneau]I'm not sure what you're talking about here. Can you screenshot?

Action: After clicking on view details for local id GTEX-14PJM-2426, it takes me to another page with Biosample Label.
- [ ] Worked
- [ ] Results as expected
-
- Other Comments:
- I followed the link to the GTEx Portal, but I am unsure of how to find the file itself. I assumed that the local id GTEX-14PJM-2426 would be the name I have to search in the GTEx portal, but it returns no results found.
This is the link and the local id listed next to the Biosample label: https://gtexportal.orgGTEX-14PJM-2426
- 

Action:
- [ ] Worked
- [ ] Results as expected
-
- Other Comments

Action:
- [ ] Worked
- [ ] Results as expected
-
- 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.

All of these tasks appear reasonable for this particular use case. I have no issues with these.

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:

Action:
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments

Action: Clicked on the Anatomy Tab on the left side of the site
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments

Action: Typed "Focal Cortical Dysplasia" in search bar
- [ ] Worked
- [ ] Results as expected
- If not, why not:

Action:
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments

Action:
- [ ] Worked
- [ ] Results as expected
- If not, why not:
- Other Comments

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.

- R00001 The interface will support GUI web access to end users
- Yes this makes sense
- R0003 The interface will support the selection of an Uberon term of interest
- Yes this makes sense
- R00004 The C2M2 model will support information relating Uberon terms to CF programs
- Yes this makes sense
- R00005 The catalog will store information relating Uberon terms to CF programs
- Yes this makes sense
- R00006 The interface will support the selection of an assay type term of interest
- Yes this makes sense
- R00007 The C2M2 model will support information relating assay types to CF programs
- Yes this makes sense
- R00008 The catalog will store information relating assay types to CF programs
- Yes this makes sense
- R00010 The catalog will store information relating projects to CF programs - Yes this makes sense
- R00011 The C2M2 model will support information relating projects to CF programs
- Yes this makes sense

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?

Search Bar did not work quite well when I wanted to search for files based on Anatomy. It works well when selecting the check boxes on the refine search table.

Did you see any spelling, grammar or similar mistakes on any resource you visited in completing your use case?
- I saw one spelling mistake on use Case
the word "addtional" (located in "Searching with FCD identifies KidsFirst addtional cohorts that included this clinical finding." )

What other comments or questions do you have about your use case?

- How would we find a specific file in the CFDE portal in DCC portal would it be as simple as clicking a hyperlink? If not a hyperlink, is there anything else that we would be given like a keyword, or Id that we can use to find the information in the DCC portal?

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
- [ ] 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
- [x] 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

### Testing user permissions functionality

If you are a Reviewer or Submitter, please try the following and document steps with screenshots (including computer clock):

- [ ] On the "Submitted Datapackage" page, I can click the pencil icon
- [ ] I can edit 1 or more field(s) for the Submitted Datapackage - please specify which field(s)
- [ ] I can change the "DCC Approval Status"