THE ROLE OF SOFTWARE TESTING FOR TEAM DEVELOPMENT

The peculiarities of software product testing processes while working in the Scrum-team were studied. The types of testing characteristic of the flexible testing technique are singled out, that make it possible to make the testing process constantly integrated into teamwork, both at the stage of requirements formation and design, and at the stage of coding and generation of test sets. This is possible by making the tester's recommendations in the process of creating user stories, planning the release of the software version in terms of testing and defects, planning a sprint based on user stories and defects, performing a sprint with continuous testing, regression testing after sprint ends and reporting of results of testing. The article highlights the stages of the flexible testing process in the Scrum team. It is proposed to automate the process of flexible testing for a training team project in the Visual Studio software environment based on Team Foundation Server. Author demonstrates an example of automation of the process of flexible testing by dividing it into four quadrants to comply with the principles of working on a flexible methodology of software development. In the first quadrant there is a study of the quality of the internal code of the software product, the modular testing. To implement modular testing in Visual Studio, a new solution is created in order to generate a class for testing, where the conditions for testing are prescribed in the body of the class. The second quadrant implements the principles of system testing. At this stage the features of creating such a test artifact as test cases are demonstrated. That provides for the fulfillment of certain conditions to verify the functionality of the developing software product; linking between created test cases to user stories presented as team project tasks Product Backlog. The study demonstrates an example of manual testing using a special tool Microsoft Test Manager, which allows you to create plans, add and update test cases, perform manual tests. In the third quadrant, it was performed a trial test in Microsoft Test Manager and it was created another test artifact - error reports. The fourth quadrant automatically tests non-functional software requirements.

TEST COVERAGE ENHANCEMENT USING HYBRID MODULAR APPROACH FOR WEB BASED APPLICATION

Automation testing may be a process that compares the particular results to the specified outcome within the software application. Automation testing is one of the foremost effective ways to check web-based applications since it allows you to hide more scenarios in less time. Selenium is one every of the foremost popular and effective automation frameworks that have been widely used for automating the testing of applications. The modular testing framework is one of the techniques used for automated testing, in which test scripts are built by breaking down the entire application into smaller pieces. Multiple data sets cannot be used thanks to hardcoded data within the test scripts. In this paper, a hybrid approach of keyword-data driven strategy is presented, in which the test data and script are separated to allow for various datasets and greater coverage. Furthermore, for improved test coverage, this split procedure is used across many modules.

ACTUALITY OF CONDUCTING MODULAR TESTING IN SOFTWARE DEVELOPMENT

The testing process in creating software, as a separate stage, has its own life cycle. The testing lifecycle is part of the entire software cycle, and they must be synchronized with each other. Designing and developing testing in creating new software systems is a complex and time consuming task. The work of any software system is organized as a set of modules that can perform various functions. To ensure the correct operation of the system as a whole, you must first test each software module separately. In case of defects, this procedure will make it easier to identify the problem in the modules and completely eliminate the relevant shortcomings. Testing all modules separately is called modular testing. The article examines the main aspects of modular testing. The software life cycle is considered and the stages of the computer program development cycle are graphically presented. It is investigated that one of the most important stages is the stage software testing. The main definitions concept of "testing" are analyzed in detail and the main types of testing process are listed. It is established that modular testing is one of the most important types of testing. Modular testing is considered to be the simplest step in testing the entire system because the modules to be tested are usually small in size. When using this method, the complexity of creating test cases increases. To put the whole system into operation, you need to set the values of the test variables correctly, and to bring part of the real system to the required state, you need to run the whole scenario. However, modular testing is associated with significant problems, which are explored in the article. The main tasks and approaches to modular testing are evaluated. The article thoroughly reveals the characteristics of modular testing as a method of structural testing.

Impact of Testing Activities on Small Modular Reactor Total Capital Investment Cost

The use Total Capital Investment Cost (TCIC) as a figure of merit to evaluate the design of a Nuclear Power Plant can help lead to more economically competitive designs. TCIC includes costs of equipment, labor, materials and the associated time value of capital. The team developed the software tool EVAL, which is capable of determining TCIC impacts for any nuclear island (NI) of any design. EVAL was first used to estimate the effect of modularization on TCIC in constructing the Westinghouse Small Modular Reactor (SMR). In particular, three different construction cases were identified. In the first case, modules are manufactured in the fabrication facility and assembled into Super Modules (SMs) in the on-site assembly area, while SMs are assembled in the hole to form the NI. The second case differs from the first case in the fabrication process, as modules are manufactured in the on-site assembly area. In the third case, the NI is ‘stick built’; i.e., the modules are assembled in the hole, where all connections are performed and the structures are built. The analysis highlighted the positive impact of off-site modular construction on TCIC. EVAL is based on an open evaluation methodology. In this paper, we present an extension of EVAL that aims to analyze the impact of testing on TCIC. As only few Nuclear Power Plants (NPP) were built in the recent years, testing costs and durations are characterized by a high uncertainty. EVAL was used to evaluate the impact of testing on TCIC, considering a range of realistic data points. Testing costs were expressed as a percentage of total labor costs and TCICs were calculated for the three construction strategies. EVAL was also used to evaluate the impact of modular testing on TCIC. Modularization allows functional testing and system testing activities to be moved from the installation stage to the fabrication and assembly stages, with a subsequent reduction in labor cost and total construction time. TCIC sensitivities were performed on the fraction of testing activities that can be moved from the installation stage. The number of these activities is dependent on both the design and the technologies used during construction. The analysis showed the positive impact of modular testing on TCIC and demonstrated how EVAL can be a tool capable of helping stakeholder decisions.