A change to a system, however small, can lead to several accidental effects, which are often not obvious and easy to identify.
SAMPLE TEST CASE TEMPLATE IN EXCEL FORMAT SOFTWARE
Two basic activities in software maintenance are the understanding of the system and the assessment of the potential effects of a change. It has been recognized as being a tedious step in software development process. Software maintenance is the most demanding and effort-consuming phase in software development. The distribution of testing tasks among mobile agents reduces the average time required for generation of test cases in regression testing. Additionally, agents developed in Java Agent Development Environment are used to collect these changes from different stake holders in the distributed environment. It is found that the use of UML class diagram, use cases and activity diagram results in better identification of changes and hence leads to efficient test case generation.
SAMPLE TEST CASE TEMPLATE IN EXCEL FORMAT CODE
We compared UML class diagrams, use cases and activity diagrams of old and modified code to identify these changes. In this research, we have used the combination of UML class diagram, use cases and activity diagram to identify changes at both syntax and semantics level. The use of modeling based UML class diagram identifies changes at syntax level, whereas use cases and activity diagram identify changes at semantic level.
In Regression testing, test case generation is a process of generating test cases from the existing test suite to ensure that modifications made in the system have not affected its existing functionality.
0 kommentar(er)
