Difference between revisions of "Quality Assurance"

Revision as of 22:05, 9 November 2017

The Quality Assurance (QA) team member is the resident expert on the gene data, ID systems, and formats. He or she should be proficient with Google Chrome Developer tools, code-savvy editors, curl, and the command line in general (as applicable) to check his or her team’s deliverable for accuracy, bugs, or any other quality-related issues. The QA is the bridge between the coders and the Data Analyst, integrating information from both parts of the team.

In many cases, the same person holds the role of Project Manager and Quality Assurance, as these two roles go together as the ones who ensure that their team’s deliverable meets the overall project’s requirements.

Guild Members

• Page Design: Hayden
• Gene Database APIs: Corinne
• JASPAR API: Quinn
• Interaction and Integration: Katie

Milestones

Milestone 4: On-going Testing of Respective Team Deliverables

The rest of the semester is expected to be an on-going process of verifying and validating the correctness of a QA member’s assigned team. Specific concerns include but are not limited to the following:

• Page Design team: Open the prototype web page and check it for correctness and clarity. The Data Analysis guild should also be consulted to make sure that the page design and layout meets their needs when they perform their respective Data Analysis tasks.
• Gene Database APIs and JASPAR teams: Manual testing will involve some combination of curl and web browser developer tool use in order to get to know the data returned by the various web services. The Coder members should find ways to show the Quality Assurance members the work-in-progress data returned by getGeneInformation, which QA can then compare to the raw web service API calls for accuracy. After the first integration milestone, QA members can examine the behavior of the prototype gene page at both the end-user and Developer Tools levels (i.e., examining network traffic to make sure the correct requests are going out with the expected responses coming in; inspecting the gene page elements to make sure that they received the correct data).
• For the Interaction and Integration team, prior to the first integration, QA can make sure that the “click-to-open-the-page” functionality works well and is bug-free. After the first integration, QA should work through the whole cycle of opening a gene page and examining the data that appear. QA should open multiple gene pages in the same session to make sure that successive gene page openings do not “step on” each other or leave behind obsolete data that “pollutes” future gene page loads.