Testing

Question 1

Why do we test our products?

Answer 1

To identify the correctness, completeness and quality of developed computer software. Testing allows us to find errors in software so they can be corrected before the product is released to the end users.

Question 2

How do we test our products?

Answer 2

Through a combination of white-box and black-box testing. White-box testing is done by the developers using automated tests, based on knowledge of how the system works.

Black-box testing is done without any for what goes on in the code, it tests the inputs and corresponding expected outputs, whether this be of single methods or the entire system. This means that black box testing can take place in both unit-, integration- and system testing.

Question 3

What are unit-, integration-, system- and acceptance tests?

Answer 3

• Unit testing focuses on a testing a single method as part of a class and interacting methods within the same class
• Integration testing focuses on testing interacting methods between classes
• System testing checks the behaviour of a complete and fully integrated software products based on the software requirements.(Black box) Is often manual and focuses on user-visible actions
• Acceptance testing checks if the software meets the customer requirements or not. It is done by both testers and developers and is onlly focused on functional testing. It contains Alpha and Beta testing.

Question 4

How do we get from a use case to a test case?

Answer 4

We generate scenarios based all possible combinations of the main flow of events and the alternate flows. The scenarios are then analyzed and reviewed to identify the conditions or data elements required to execute various scenarios. When all necessary elements and conditions have been found, specific data is substituted into the places of the data elements

Question 5

What are equivalence classes and boundary values?

Answer 5

We use equivalence classes to reduce the total number of tests cases by focusing on boundary values and thereby still covering maximum requirements.
Equivalence classes are subsets of input data where testing one value would be the same as testing any other. They can be split into valid and invalid. The boundary values are tested to cover our edge cases. We test both right above and below the boundary, meaning that we test the upper and lower valid and invalid boundaries, to ensure that the system accepts all valid equivalence classes and no invalid ones.