3_24_2020 Lab Meeting

Need to submit two things. Assingments --> Sprint 3 --> Submit Assignment Should upload the test plan (1 per group) Also submit the URL to the demo Video. Should have fully functional 3 core features of twitter-like website. Youtube, vimeo, or whatever video platform. Grade based on content in demo.

Going over test template. At least 2 people making changes. Everything should be brief. Just google stuff you don't know, or ask me (Anh). Workflow, methodologies; depends on how you're doing your testing.

Scope; depends on what you're going to test. Everything you test should be in the scope. Anything you don't test goes in "out of scope" and you need to give reasons (hopefully good ones) about why you can't . time constraints, general inability do to restrictions, etc.

Examples of Objectives. Has to be quality guarantees. What qualities are you testing of the software? should not be just "have a website" but would need to be "have a website with a minimum number of bugs" for example. Has to be about enhancing quality. Testing does not help you have a website, but to help the quality of the website.

Roles and Responsibilites: Very similar to the group, but are more test-oriented. Roles should be different from development roles.

Test methodologies - nice to have. Can put links to the methodolgies in there.

Test levels: list the testing levels. Unit tests, integrations test, system tests, etc. Some teams may not have integration tests Testing levels will vary from team to team

Bug Triage: need to explain what is meant by each level of severity Need to describe what the plan is to fix the bug

N/A Can use

Test completeness All tests should be executed A test should be considered complete if

Run tests, find bugs, run tests, find fewer bugs, run tests, etc. until no bugs. Then testing is complete.

3- Test deliverables

Bug reports can be generated automatically based on what framework you use. you don't have to submit the bug reports until the end of the semester. Going to look to see how many test cases pass/fail, and how many have been written.

4 - Test Environment

List testing framework(s) Need to list everyhting so that someone can remake the environement later

When find bug, should create an issue on GitHub. Every bug should be able to be replicated Should mention all the steps to replicate/reproduce the bugs. So other can follow your steps. So have that in the issue You don't have to mention all the bugs on the test plan. the test plan is very general