Software testing2

How would we test unit?

To test a unit in isolation, we create mock objects to represent components that are external to the unit.

Test driver

simulates a part of a system that invokes operations on the unit

Test stub

simulates a part of a system that is called by the unit

Unit testing cycle

1. Create the unit, test driver and test stub(s)

2. Have the test driver invoke an operation on the unit

3. Ensure that the unit behaves as expected

Test Case Method Naming

<method_name>_<Startingstate>_<expected_result>

Integration Testing

Tests how components of a system interact with each other

Tyoes of intergration tests

1. Horizontal integration Testing: Focuses on testing layers of a system, with new layers incrementally added to a test

2. Vertical Integration Testing: Focuses on testing scenarios or user stories

Types of Horizontal Intergration Tests

1. Top-down testing: highest level subsystems are tested first.

2. Bottom-up testing: lowest level subsystems are tested first.

3. Sandwich testing: combines top-down and bottom-up approaches. Testing converges on a target layer.

Big bang intergration

all units are linked at once and the entire system is tested

Front-end component testing encomposes

1. Snapshot Testing

2. Accessibility Testing

3. Visual Regression Testing

4. End-to-End Testing

   SAVE

Continuous Integration (CI)

a software development practice where code changes are frequently integrated into a shared repository, typically multiple times a day

Each integration triggers automated build and testing processes to detect and address integration errors as early as possible in the development lifecycle

What happens everytime a new build is generated?

1. Run unit tests on changed components

2. Run regression tests on unchanged components to ensure they still work as intended

3. Run integration tests on the system

Continuous integration tools

1. GitHub Actions

2. Azure DevOps Pipelines

3. Travis CI

Quality Tests

1. Timing testing – test response times

2. Recovery testing – test how system responds to errors or lack of data etc.

3. Volume testing – test with large volumes of data

4. Stress testing – test beyond the normal limits of a system

Degrees of acceptance testing

1. Alpha Tests – client uses software in development environment Developers on hand to fix issues

2. Beta Tests – conducted in production environment. Small subset of user base chosen to use system