Electronic Health Record System 

Integrated testing

This is the testing phase that evaluates a combination of a system’s different modules or units to identify areas that do not function properly for improvement (Mahajan & Pune, 2016). It also tests the compliance of the integration of the units based on the requirements of the client. It is done after the unit testing but before the validation of the entire software. It combines the units and tests them as larger aggregates of the system. In EHR-integrated testing, the bottom-up testing approach will be utilized (Singh & Khan, 2012). This approach involves testing the lowest units first, and then this is used to help in the testing of higher ones.

This process is continued until the units at the highest level of the system hierarchy are tested. All the lowest level units are integrated and then tested for defection, and this process is repeated upwards, identifying the areas of improvement along the hierarchy. This testing approach will be useful to us because all the modules of the EHR system are already completed waiting for the testing that will be done and validation. The process will also help report the level of development of the software and the process of the testing activity to help in planning as it gives a percentage of completion. Through this methodology, the areas of weakness will be identified for correction.

Stress Testing

This type of software testing reports on the suitability and reliability of certain software to the intended functions. This test verifies the system’s robustness and ability to handle errors under extreme and heavy load conditions (Hassan, 2015). The EHR stress testing will enable the team to verify if the software will be ideal to perform the functions intended by the client for successful installation and validation. The testing will also ensure that the limits of the software are identified to help avoid crushing during the actual functioning. It is also referred to as endurance testing.

In the stress testing, we will do the testing plan by gathering the system data, analyzing it, and defining the testing goals. An automation script will also be created to generate the data for the scenarios for stress. The script will then be executed to develop the testing results.  The test results will be analyzed to identify the bottlenecks noted in the system. Finally, the system will be fine-tuned and optimized to have the ability to perform the intended function, with the users having full knowledge of the ability of the EHR systems and its limits.

References

Choudary, A. (2019, November 28). What is unit testing? Everything that you need to know about unit testing. Retrieved July 24, 2020, from Edureka. co: https://www.edureka.co/blog/what-is-unit-testing

Hassan, A. E. (2015). A Survey on Load Testing of Large-Scale Software Systems. IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 41, NO. 11, NOVEMBER 2015, 1091-1117.

Mahajan, P., & Pune, B. v. (2016). Different Types of Testing in Software Testing. International Research Journal of Engineering and Technology (IRJET) Volume: 03 Issue: 04 | Apr-2016, 1661-1664.

Munot, K. (2019, November 15). Unit Testing-Important role in software development. Retrieved July 24, 2020, from Medium.com: https://medium.com/nonspio/unit-testing-important-role-in-software-development-1f52f7c810f8

Singh, R., & Khan, I. A. (2012). AN APPROACH FOR INTEGRATION TESTING IN ONLINE RETAIL APPLICATIONS. International Journal of Computer Science & Information Technology (IJCSIT) Vol 4, No 3, June 2012, 141-158.