Automated Test Activity for Software

Wireless Maingate is focused on the communication machine to machine. This involves a billing system, Geneva, and own applications made by the company. The test system is complex when the different parts are working together. This means that the company works with different operation systems and variety of databases. The biggest part involves Java, Oracle and LDAP (Lightweight Directory Access Protocol).The two parts we have been focused on during our study is their billing system, but more important their own application in Java. The Java application is a self-care system for their clients to easily control and make changes on the web.


Software producing companies want to increase their quality and efficiency. They often look at automated test tools as a part of a solution. Not many company’s use test tools, the time it takes to evaluate which test tool that suites the company best costs much in both money and time. The development process within the IT world is so fast, this makes it difficult for any enterprise to put money in a test tool that may be useless within a few years. For a test tool to be valuable for a company it must be used during at least a few years. An automated test takes a lot of time to implement and introduce in the company.
To get the whole picture when to automate test we have looked at different test methodologies. Step-by Step Method uses tables and lists to create the test document. Product Life Cycle Method (CPU) describes implementing of software test in the product life cycle. Well-developed test methods can save a lot of time and make it possibly for developers to work effectively.We have also investigated some general information about automated test like cost and when to automate. ATLM (Automated Test Life-Cycle Methodology) is a methodology that is used in order to take the correct decisions such as when to automate or not, (ATLM) is a structured methodology aiming toward ensuring a successful implementation.We have also described some methods of automated tools…..


3 Introduction
3.1 Short presentation of Maingate
3.2 Intended readers
3.3 Problem Area
3.4 Purpose and Goal
4 Basic facts about Manual Tests
5 Different Test methodologies
5.1 The Step – by – Step Method
5.1.1 List Test Requirements based on the Specifications
5.1.2 Add Test Requirements for a range of inputs
5.1.3 List a Test Type for each Test Requirement
5.1.4 Review Test Types and fill in the holes
5.1.5 Write a Test Case for each Test Requirement
5.1.6 Group Test Cases into Test Scripts
5.2 Product Life Cycle Method
5.2.1 Design Phase
5.2.2 Code Complete Phase
5.2.3 Alpha Phase
5.2.4 Beta Phase
5.2.5 Zero Defect Build Phase
5.2.6 Green Master Phase
5.3 Summary
6 General facts about Automated Tests
6.1 Automated Test Lifecycle Methodology (ATLM)
6.1.1 Decision to Automate Test
6.1.2 Test Tool Acquisition
6.1.3 Automated Testing Introduction Process
6.1.4 Test Planning, Design and Development
6.1.5 Execution and Management of Tests
6.1.6 Test Program Review and Assessment
6.2 When should a Test be automated?
6.3 To introduce Automatic Tools
6.4 What is required to Successfully Implement Automated Testing?
6.5 The Costs to Automated Test
6.6 Cost Effective Automated Testing
6.7 Automated Tests Survival
6.8 Losing with Automation
6.9 Summary
7 Preparation before installing an Automated Testing Tools
8 Evaluation of Automated Tool methods
8.1 The Record/Playback Method
8.1.1 Advantages
8.1.2 Disadvantages
8.2 The “Functional Decomposition” Method
8.2.1 Advantages:
8.2.2 Disadvantages:
8.3 The Key-Word Driven or Test Plan Driven Method
8.3.1 Advantages:
8.3.2 Disadvantages:
8.4 Summary
9 Automated Tools
9.1 Introduction
9.2 Rational
9.2.1 Rational Test tool
9.2.2 Rational Tools
9.2.3 Rational Package
9.2.3 Summary
9.3 Segue Software Inc
9.3.1 SilkTest – Automated Functional and Regression Testing
9.3.2 Silk Performer
9.3.3 SilkPilot
9.3.4 SilkRadar
9.3.5 Summary
9.4 Mercury Interactive’s WinRunner
9.4.1 Support for functional testing of WAP applications
9.4.2 Easy Verification of Transactions
9.4.3 Sophisticated Introspection Capabilities
9.4.4 A simpler Test Creation Process
9.4.5 Problems with WinRunner
9.4.6 Test Developers Pronouncement
9.4.7 Working with WinRunner
9.4.8 Summary
9.5 Summary of test tools
10 Result and Conclusion
10.1 Comparison between Manual and Automated testing
10.2 To make Wireless Maingate Testing more Efficient
10.4 Conclusions
10.5 Future work for Wireless Maingate
11 Definition of terms
11.1 Ad Hoc Testing
11.2 Automation Testing
11.3 Black Box Testing
11.4 Boundary Testing
11.5 Breadth Testing
11.6 Compatibility Testing
11.7 Functionality Testing
11.8 Functional Localisation Testing
11.9 Integration Testing
11.10 Interoperability Testing
11.11 Install Testing
11.12 Load Testing
11.13 Performance Testing
11.14 Regression Testing
11.15 Storage Testing
11.16 Stress Testing
11.17 Syncopated Testing
11.18 System Integration Testing
11.19 Unit testing
11.20 Volume Testing
11.21 White Box Testing or Glass Box Testing
12 References
13 Appendix
13.1 Rational
13.1.1 System requirements for Rational Suite TestStudio
13.1.2 System requirements for Rational TeamTest
13.1.3 Price for Rational Robot
13.2 Segue Software Inc
13.2.1 SilkTest
13.2.2 Silk Performer
13.2.3 SilkPilot
13.3 Mercury Interactive
13.3.1 WinRunner
13.3.2 Tips for WinRunner Interested

Author: Ann-Chatrin Djurström, Ewa Holgersson, Isabell Jonsson

Source: Blekinge Institute of Technology

Reference URL 1: Visit Now

Leave a Comment