My Role in Testing PIS
As a Software QA Engineer, I played a key role in testing the PIS (Public Information System), a sophisticated software solution designed for managing and controlling smart signs in real-time. My involvement in this project encompassed extensive Integration Testing, Functional Testing, Non-Functional Testing, and Regression Testing, ensuring the robustness, reliability, and overall quality of the system.
Integration System Testing
I performed comprehensive integration system testing to validate the interaction and seamless communication between various integrated system modules. During the development process, I employed Incremental Integration testing to progressively test module interactions. Upon completion of individual module testing, I utilized Big Bang Integration to assess the combined operation of all modules.This process included rigorous API integration testing for real-time communication with the Urban-View server, ensuring precise data retrieval, transmission, and the application of a variety of settings and configurations. My primary objective was to ensure smooth interoperability across critical system components, including FFSB, real-time transit information, environmental monitoring, camera access, and dynamic lighting control.
Functional Testing
My functional testing efforts were focused on validating that the PIS system's features and functionalities work as intended. This included:
- Black Box Testing: I developed and executed comprehensive test cases that focused on the input-output functionality of the system without delving into the internal code structure. This approach ensured that the PIS system met all user requirements.
- Equivalence Partitioning: I applied this testing technique to divide input data into equivalent partitions and created test cases to cover each partition, ensuring efficient test coverage and minimizing redundant test cases.
- Decision Table Testing: To validate complex business logic, I used decision tables to test different combinations of inputs and their corresponding outputs, ensuring that all possible scenarios were covered.
Non-Functional Testing
To ensure the PIS system's robustness and reliability, I also conducted various non-functional testing types:
- Performance Testing: I evaluated the performance of the PIS system under different loads to ensure it could handle the expected traffic and data processing in real time. This involved checking response times, throughput, and resource utilization.
- Stress Testing: I tested the system's stability by pushing it beyond its normal operational capacity to identify its breaking point and to ensure it could recover gracefully without crashing.
- Recoverability Testing: I assessed the system’s ability to recover from crashes, failures, and other interruptions to ensure that it could maintain continuous service without data loss or significant downtime.
- Documentation Testing: I reviewed and tested all system documentation, including user manuals, technical guides, and API documentation, to ensure that they were accurate, complete, and easy to understand.
Regression Testing
I conducted thorough regression testing to ensure that new changes, updates, or bug fixes did not adversely affect the existing functionalities of the PIS system. This involved re-running previously executed test cases on each new build and validating that the system's core features—such as real-time transit information, environmental monitoring, and system configuration—remained stable and functional. The goal was to maintain a high level of quality and reliability throughout the development lifecycle.
My comprehensive testing efforts helped ensure that the PIS (Public Information System) was a robust, efficient, and reliable solution capable of enhancing the smart city ecosystem. By performing extensive integration, functional, non-functional, and regression testing, I contributed to delivering a high-quality product that optimizes resource usage, provides valuable public information, and maintains high operational standards.
