Black Box Testing / Test Cases

Question 1

What are test to pass cases?

Answer 1

Testing all of the cases that should pass based on the spec sheet.

Question 2

What things should you be testing in the test to pass cases?

Answer 2

Test the upper and lower limits, all given parameters (+, -, * in the math one), negatives and positives, all variables at least once, and test for the things the spec sheet says the program should not do. If a test case fails, then do multiple tests trying to pinpoint the cause/root of the failure.

Question 3

What things should you be testing in the test to fail cases?

Answer 3

Test for things not mentioned in the spec sheet that you think might break the program. Test for things that you expect to throw an error or do nothing.

Question 4

What columns should be expected in both the test to pass and test to fail reports?

Answer 4

The test case number The actual test case parameters tested The reason for the test case The expected result The observed result If the test case passed or failed

Question 5

What columns should be expected in the bug report?

Answer 5

The bug id Test cases that show the bug The explanation of the bug

Question 6

What are the 6 black box testing design techniques?

Answer 6

• Equivalence Partitioning
• Boundary Value Analysis
• Decision Table
• State Transition
• Exploratory Testing
• Error Guessing

Question 7

What is equivalence partitioning?

Answer 7

You divide test conditions into groups, which we test only one condition.

eg. only tested *, +, -, blue once and assumed it worked throughout the rest of the application

Question 8

What is boundary value analysis?

Answer 8

We test the boundaries, not every possibility inbetween them.

eg. if boundaries at > 10 and < 20 we would test for 9,10,11,19,20,21

Question 9

What is the decision table technique?

Answer 9

This test technique is appropriate for functionalities which has logical relationships between inputs (if-else logic). We consider conditions and actions.

eg. login page validation (Allow user to login only when both the user id and password are entered correct).

Conditions: Enter valid User ID, Enter valid password.

Actions: Displaying home page, Show a message “Invalid Creds.

Question 10

What is the state transition technique?

Answer 10

Testing the state transition. Meaning if I put a value in, that is supposed to either carry on to the next step or clear the value after, make sure it does that.

Question 11

What is exploratory testing?

Answer 11

This is when the system is tested by someon who has no idea about the requirements, and is simply learning the system by exploring, finding bugs in the process in how things should work logically.

Question 12

What is the error guessing technique?

Answer 12

Unplanned testing based on the testers prior experience, testing things that they have seen break systems and they think might break the system, failure testing.

eg. submitting a form with missing values or invalid values

Question 13

What is the bug report checklist?

Answer 13

1. Reproduce the bug 2 - 3 times
2. Make sure the bug hasn’t already been reported
3. Write the detailed bug report
   
   • DefectID
   • Title/Summary
   • Reporter Name
   • Defect Reported Date
   • Who Detected
   • How detected (testing, accidentally, giving walkthrough)
   • Project Name
   • Release/Build Version (system build #)
   • Defect/Enhancement
   • Environment (windows 8, chrome 48)
   • Priority
   • Severity
   • Status (new, open, rejected)
   • Description (what were you doing when the bug shows
   • Steps to reproduce (detailed!! even include browser)
   • URL
   • Expected Result
   • Actual Result
   • Attachments
   • Defect close date