Use Case 6 Gathering Blood Cancer Data sets

# Use Case 6 Gathering Blood Cancer Data sets # Use Case Testing form **Reviewer**: Jose Sanchez **OS (including version)**: Windows 10 (1909) **Browser (including version)**: Google Chrome **Use case**: [Use Case](https://use-cases.nih-cfde.org/uc-0006/) **Review type**: <Selenium> **Role groups**: # Use Case Test <details><summary>Instructions</summary> 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 </details> ## Use Case Description **1. Evaluate the description.** - Does this description make sense? 1. Navigates to the cfde portal 2. Searches by Biosample 3. Filters that list by Anatomy 4. search for blood and venous blood 5. Keep WGS and RNA Seq Assay Values 6. Project Filter - search belongs to 17 projects 7. Read Project information and narrow down to two projects 8. Export Files - Does it sound like a useful thing to do? - I agree that it sounds useful to check multiple WGS data from multiple Common Fund Programs to study the wide spectrum events that are involved in AML. - Are there any corrections that should be made (spelling, grammar, etc)? - None that I can tell. **2. Try to complete the steps as they are described for the persona in the use case.** <details><summary>Instructions</summary> 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 </details> Action: Started on the home page https://app-staging.nih-cfde.org/, Log in using gmail account - [x] Worked - [x] Results as expected - If not, why not: - Other Comments Action: Click View Data By "BioSample" - [x] Worked - [x] Results as expected - If not, why not: - Other Comments Action: Clicked on venous blood and blood in Refine Search & Anatomy. - [x] Worked - [x] Results as expected - If not, why not: - Other Comments Action: Clicked on whole genome sequencing assay & RNA-se assay - [x] Worked - [x] Results as expected - If not, why not: - Other Comments Action: Clicked on Search By Project - [x] Worked - [x] Results as expected - If not, why not: - Other Comments Action: Clicked on GTEx and TARGET: Acute Myeloid Leukemia - [x] Worked - [x] 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. - Tasks appear to be straightforward. It is pretty easy to filter through the refine search filter.(checkboxes) t-0001: Access CFDE interface - Works through Refine Search(checkboxes) t-0018: Search/filter data sets by biosample - Works Through Refine Search(checkboxes) t-0006: Search/filter data sets by anatomic terms - Works Through Refine Search(checkboxes) t-0005: Search/filter data by assay type terms - Works Through Refine Search(checkboxes) t-0019: Search/filter data sets by project - Works Through Refine Search(checkboxes) t-0003: Export a file of results - 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> 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 </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. r-00001: The interface will support GUI web access to end users - This makes sense r-00002: The interface will support user authentication - This makes sense r-00034: The interface will support the selection of a biosample of interest - This makes sense r-00035: The C2M2 model will support information relating biosamples to CF programs - This makes sense r-00036: The catalog will store information relating Uberon terms to CF programs - This makes sense r-00003: The interface will support the selection of an Uberon term of interest - This makes sense r-00004: The C2M2 model will support information relating anatomy terms to CF programs - This makes sense r-00005: The catalog will store information relating anatomy terms to CF programs - This makes sense r-00006: The interface will support the selection of an assay type term of interest - This makes sense r-00007: The C2M2 model will support information relating assay types to CF programs - This makes sense r-00008: The catalog will store information relating assay types to CF programs - This makes sense r-00010: The catalog will store information relating projects to CF programs - This makes sense r-00011: The C2M2 model will support information relating projects to CF programs - This makes sense r-00014: The interface will support end user download of tables and figures in common formats - 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> 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 </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? None Did you see any spelling, grammar or similar mistakes on any resource you visited in completing your use case? None What other comments or questions do you have about your use case? None What other comments or questions do you have about any of the resources you visited? None What feedback do you have about this form/testing process? None # 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 - [ ] 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

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.