CampusLearn
← BIT 302 Software Engineering

Testing, Version Control and Continuous Integration

Notes

Testing at different levels Software testing evaluates behaviour against expectations and exposes defects before they affect users. Unit tests target small components in isolation; integration tests check cooperation between components; system tests examine complete workflows; acceptance tests assess business needs. Regression testing reruns checks after changes to detect previously working behaviour that has broken. Boundary values and invalid inputs deserve explicit attention because typical inputs alone give weak coverage. A passing test suite does not prove the absence of defects: its value depends on relevant assertions, realistic conditions and coverage of important failure paths. Collaborative delivery controls Version control records changes and supports collaboration through commits, branches and merges. A commit should represent a coherent change with an informative message. Code review helps detect defects and share knowledge before merging. Continuous integration (CI) automatically builds and tests integrated changes frequently, providing rapid feedback rather than postponing compatibility checks until release. A pipeline should use controlled dependencies, protect secrets and block integration when critical checks fail. Continuous delivery keeps software ready for release, whereas continuous deployment automatically releases qualifying changes. Neither approach removes the need for business approval where policy requires it. Practical example An Eldoret SACCO application calculates a 2 percent processing fee. A KES 15,000 request should produce 15,000 times 0.02, or KES 300. A unit test checks this calculation, an integration test verifies saving the fee with the loan, and an acceptance test checks the complete member application flow. Suppose a CI suite runs 120 tests and three fail after a merge request. Its pass rate is 117 divided by 120 times 100, or 97.5 percent. The team still investigates the failures before merging, especially if they affect fees; a high percentage is not permission to ignore financial defects.

Quiz

1. A CI run passes 117 of 120 tests. What is the appropriate conclusion?

2. Which test best checks that a calculated fee is saved correctly in the database?

3. What distinguishes continuous deployment from continuous delivery?

Sign in to submit and securely grade your quiz.