Software testing is a critical discipline within ICT technician roles in Kenya, ensuring that computer software meets the required standards of quality, reliability, and functionality before deployment. In environments ranging from county government offices to retail businesses, effective software testing prevents costly failures and enhances user satisfaction. This chapter explores the principles, techniques, tools, and practical steps involved in testing computer software, empowering ICT technicians to deliver robust software solutions that support Kenya’s digital transformation initiatives.

2.1 Software testing

Software testing involves systematically evaluating a software application to identify defects, verify that it functions as intended, and ensure it meets user requirements. For ICT technicians, rigorous testing is essential to safeguard data integrity and operational continuity. Testing mitigates risks associated with software failures, which can disrupt services and undermine stakeholder trust.

2.1.1 Importance of software testing

The role of software testing extends beyond defect identification to encompass quality assurance and user experience enhancement. Testing validates that software behaves correctly under various conditions, which is vital where software supports critical business operations.

Ensuring software reliability

Reliable software minimises unexpected crashes or errors, which is crucial for systems such as payroll or stock control, where downtime can halt daily work. Testing simulates real-world scenarios to confirm software stability.

Enhancing security

Testing uncovers vulnerabilities that could be exploited by cyber threats. For example, an online payment application is tested for weak password handling and unprotected data so that client financial details are not exposed.

Verifying compliance with requirements

Testing confirms that software complies with specifications and regulatory standards, such as data protection requirements that apply to personal information held in a system.

Reducing maintenance costs

Identifying defects early reduces costly post-deployment fixes. For instance, a retail business that thoroughly tests its point-of-sale software avoids expensive downtime and customer dissatisfaction.

Improving user satisfaction

User acceptance testing ensures the software meets user expectations, which enhances adoption rates and productivity. For example, staff who try a new invoicing application before release can point out confusing screens that the developers can correct.

2.1.2 Computer software testing techniques

Testing techniques provide structured approaches to assess different software aspects, enabling ICT technicians to apply appropriate methods depending on project scope and complexity.

Black box testing

In this technique, testers evaluate software functionality without knowledge of the internal code structure. It focuses on input-output behaviour, which is useful when validating the user interface of an application such as a stock control system: enter a quantity, press save, and check the result.

White box testing

White box testing requires understanding the internal logic and code paths. It helps identify hidden errors in algorithms or data handling, for example a wrong rounding rule inside the calculation module of a payroll application.

Regression testing

Regression testing ensures that new code changes do not adversely affect existing functionalities. This is particularly important when updating an inventory system with a new reporting feature, so that stock entry and sales screens keep working as before.

Performance testing

This technique assesses software responsiveness and stability under load. For example, testing an e-commerce platform during simulated high traffic protects against crashes during peak sales. Tools such as JMeter can simulate many concurrent users for this purpose.

Usability testing

Usability testing evaluates how easily end users can navigate and operate the software. For example, a technician observes whether a first-time user can complete a transaction in a mobile money application without help, which shows whether the screens are clear and effective.

2.1.3 Computer software testing tools

Effective software testing relies on tools that automate, facilitate, or enhance the testing processes, enabling ICT technicians to work efficiently and produce reliable results. The tools below cover automated testing of desktop, web, mobile and API-based software.

2.1.3.1 TestComplete

TestComplete is a commercial automated testing tool that checks the user interface of desktop, web and mobile applications. It can record the actions of a tester and replay them as a script, so the same check can be repeated after every software update. For example, an ICT technician can record the steps of posting a customer payment in a desktop accounting application and replay them each time the application is upgraded.

Key features:

• Record and replay: Captures mouse and keyboard actions and turns them into a test that can be run again without manual effort.
• Keyword-driven testing: Lets testers build tests from visual keyword steps, so staff with limited programming skill can create tests.
• Scripting support: Allows tests to be written or edited in scripting languages such as JavaScript or Python for more complex checks.
• Object recognition: Identifies screen elements such as buttons, text boxes and grids, so tests keep working when the layout changes slightly.
• Test reporting: Produces logs showing which steps passed or failed, with screenshots that help developers locate a defect.

2.1.3.2 Selenium

Selenium is an open-source tool that automates web browsers and is widely used to test web applications. It reduces repetitive manual testing for systems such as an online ordering website. Testers write scripts that open a page, enter data, click buttons and compare the result with the expected outcome.

Key features:

• Selenium WebDriver: Controls a browser directly through code, imitating how a real user interacts with a page.
• Selenium IDE: A browser add-on that records and replays tests, suitable for quick checks by beginners.
• Selenium Grid: Runs the same tests on several browsers and machines at the same time, saving testing time.
• Multiple languages: Tests can be written in languages such as Java, Python, C# and JavaScript.
• Cross-browser testing: Supports major browsers such as Chrome, Firefox and Edge, confirming that a web system behaves the same for all users.

2.1.3.3 Appium

Appium is an open-source framework for automating tests on mobile applications running on Android and iOS. It is useful where services are delivered through phones, for example a mobile money or mobile payment application. Appium tests the application as it is installed, so the code of the app does not need to be changed for testing.

Key features:

• Cross-platform testing: The same test approach can be applied to Android and iOS applications, reducing the work of writing separate tests.
• App types supported: Tests native apps, hybrid apps and mobile web pages opened in a phone browser.
• WebDriver protocol: Uses the same communication standard as Selenium, so testers who know Selenium learn Appium quickly.
• Language choice: Test scripts can be written in common languages such as Java, Python and JavaScript.
• Devices and emulators: Tests can run on real phones or on emulators, allowing checks on different screen sizes and versions of the operating system.

2.1.3.4 Postman

Postman is a tool for building, sending and checking requests to an application programming interface (API). It is indispensable for testing APIs, which are common in integrated systems where one application exchanges data with another. A technician can send a request to a customer registration service and confirm that the response contains the correct data and status code.

Key features:

• Request builder: Allows testers to send requests such as GET, POST, PUT and DELETE and view the response in a readable form.
• Collections: Groups related requests together so that a full sequence, such as login, search and update, can be run in order.
• Environments and variables: Stores values such as server addresses and tokens, so the same tests can run on test and live systems.
• Automated test scripts: Lets testers write checks in JavaScript, for example confirming that a response arrives with the expected status and fields.
• Collection runner: Runs a whole collection at once and reports passed and failed checks, supporting regression testing of APIs.

2.1.4 Performing computer software testing

Executing software testing involves a structured sequence of activities that ICT technicians must follow to ensure thorough evaluation and documentation.

1. Requirement analysis: Understand software specifications and testing objectives to define what needs validation. For instance, analyse the functional requirements of a stock management system to prepare relevant test cases.

2. Test planning: Outline the scope, approach, resources, schedule, and deliverables of testing. This includes selecting appropriate testing techniques and tools suited to the software type and user environment.

3. Test case development: Design detailed test cases that specify inputs, expected results, and execution conditions. Well-crafted test cases cover positive and negative scenarios, such as entering invalid data into an online order form.

4. Test environment setup: Prepare hardware, software, network configurations, and data required for testing. This may involve creating a replica of the client's production environment in the firm's test lab to accurately simulate user conditions.

5. Test execution: Perform the tests according to the plan, recording actual outcomes and any deviations. Automated tools may be used alongside manual testing to increase coverage and efficiency.

6. Defect reporting and tracking: Document identified defects with detailed descriptions and severity levels. Use a defect tracking tool such as JIRA to assign issues to developers and monitor resolution progress.

7. Test closure: Evaluate test completeness, prepare test summary reports, and archive test artefacts. This phase confirms that testing objectives have been met and provides insights for future projects.

Example: A software firm upgrading a client's inventory management software followed these steps to ensure the new features worked correctly without disrupting existing functions, thereby maintaining the client's trust and operational continuity.

Chapter Summary

This chapter explored the critical process of software testing, emphasizing its importance in ensuring reliable and efficient computer software. Various software testing techniques were discussed, highlighting their roles in verifying different aspects of software functionality. The chapter also introduced popular software testing tools such as Test Complete, Selenium, Appium, and Postman, explaining their specific applications in testing environments. Practical steps for performing software testing were outlined to guide systematic evaluation of software performance. In addressing issues identified through testing, the chapter covered different types of corrective measures that can be applied to fix software defects. It further examined software corrective tools that assist in implementing these fixes effectively. Finally, the chapter detailed the comprehensive approach required for testing computer software functionality, ensuring that all components operate as intended before deployment.