Test Design

Question 1

Test design guideline 1

Answer 1

Several test cases may be needed for one requirement
Eg:
Zooming in and out is done 3 ways. Each way needs one test cases

Question 2

Test Design Guideline 2

Answer 2

One test case = one test
+/- test case for zooming in out is one test case and one tes

Question 3

Tests should not duplicate functionality

Answer 3

Don’t make the tester do the same thing twice

Question 4

Test cases exist within the requirements

Answer 4

Don’t write test cases for scenarios outside what’s documented in the requirements. Eg: don’t test if you can boil a phone if you don’t need to

Question 5

Tests must cover all requirements

Answer 5

Don’t forget to make a test cases for every element of every requirement

Question 6

Software for test cases creation

Answer 6

Jira
Excel
Testrail

Question 7

Black box testing

Answer 7

Is scripted, with test cases written in advance based on requirements

Question 8

Equivalence partitioning

Answer 8

Grouping test data to reduce the number of required tests

Question 9

Partition

Answer 9

A subset of acceptable values from within a larger set
(5-8 within all integers)

Question 10

Boundary analysis

Answer 10

Test boundaries in a range and everything right above and right below the boundaries

Question 11

Decision tables

Answer 11

Allows you to map all the possible combinations necessary to test. For example, a login form with username and password

Question 12

Four rules of bug reports

Answer 12

Use cause and effect relationships
Describe the logical chain of steps
State the core issues
Structure the information

Question 13

Cause and effect

Answer 13

State what the problem is, and what probably caused it

Question 14

Describe the logical chain of steps that explains cause and rffect

Answer 14

Describe every step you took to get to the bug