# Smart Grid Testing Management Platform (SGTMP) +
## 2 Background
### The ISO/IEC/IEEE 29119 Testing Process  
Software testing standards/models provide a way to perform tests on a uniform and consistent basis [32]. Standards allow for test results to be repeatable and reproducible [33]. For the implementation and usage of SGTMP, we considered the underlying testing process that can be supported, as all the data models need to be adapted. Several benefits can be derived from the adoption of a testing standard/framework. From a general point of view, the main advantage is to define and follow processes and practices that have been applied in similar contexts and proven beneficial over time [32]. Another benefit is to ease the communication among all project stakeholders. This can refer to the standard to understand the documented steps in the process, allowing long-term process improvement.  
There are many testing process models/standards which can be adopted within an organization, and a full discussion would be outside the scope of this work. More extensive discussions about characteristics of different testing standards can be found in works by [PERSON] et al. [32], [PERSON] et al. [34], and [PERSON] et al. [35; 36], [PERSON] [37], [PERSON] [38], [PERSON] [39], [PERSON] et al. [40]. In this work, we considered the most reported models: Test Maturity Model integration (TMMi), Test Process Improvement (TPI), Critical Testing Process (CTP), Systematic Test and Evaluation Process (STEP), and ISO/IEC/IEEE 29119 [32; 34]. To support SGTMP, we selected the ISO/IEC/IEEE 29119 standard, a standard created in 2013, expected to reach full adoption in upcoming years. The standard can be used for a wide variety of application domains and levels of criticality and is not specific to any particular life cycle, so it is applicable for testing on projects using sequential, iterative, and agile approaches [33]. Extensions to the standard and adaptations are expected to emerge over the years: it is as such expected that more adaptations of standards/frameworks/methodologies will emerge in the upcoming years, possibly based on ISO/IEC/IEEE 29119, making SGTMP easier to adapt.  
The supported testing process is based on ISO/IEC/IEEE 29119 indications (Figure 1). The current implementation does not support all the steps, but SGTMP was created taking into account possible extensions. ISO/IEC/IEEE 29119 suggests that a risk-based approach is considered [41]: tests should be prioritized by the more risky components regarding impact and probability of occurrence. Test techniques are selected for each test, and test plans can be defined, containing necessary information about context, tests, the table of risks and their rating, test strategy, staffing, and scheduling. Test specifications are defined based on the design specification, case specification, procedure specification, data requirements, and environment requirements. It is important to note and store all conditions of a test run (such as particular external parameters). Once tests have been defined, they can be run by the platform by interfacing with the software and hardware devices. The test controller takes test specifications and requirements and runs the tests. When tests are executed, different reports and logs are automatically created. These are important to determine the test status results and cause of possible incidents (e.g., hardware failures).