International Journal of Innovative Research and Development

Abstract

A testing methodology is a tool or method used to test an application. A testing strategy, on the other hand, is a holistic view to how you will test a product; it's the approach you will take, the tools (and methodologies) you will use to deliver the highest possible quality at the end of a project. In software quality, the test strategy consists of a myriad of methodologies, activities, and staffing solutions. The strategy overall sets the acceptable bar and calls out how the test team will achieve that bar. It is the sum of all the inputs, in an organized plan. Testing methodologies are the different approaches you will take to testing. The purpose of this paper is to define the strategy, procedures, and tools for testing the technology enablement of the smart meter implementation program. All phases of the testing lifecycle will be covered, from Unit Testing to User Acceptance Testing. However, the primary focus is on Integration Testing of System-to-System Interfaces, End-to-End business transactions and User Acceptance Testing.  As such, the scope of integration testing includes transactions that start or terminate at vendor systems or field-devices. Then described is approach that provides assurance the release will enable the required integration interactions between the applications in order to facilitate and support “real-life” business transactions. This lifecycle starts with the application or system specific tests performed by application developers and infrastructure engineers (unit / string tests) and does not end until the business owners have given their approvals after user acceptance testing. The focus of integration testing is to verify that the applications that are linked together successfully enable “real-life” business transactions.

Keywords

Full Text