UNIT-5

Categorization of Testing Tools: Static tools perform the following types of static
analysis
Static Testing Tools: Control Flow Analysis, Data use Analysis,Interface Analysis, Path
Analysis
Dynamic Testing Tools: Program Monitors
Testing Activity Tools: Tools for Review and Inspections, Tools for Test Planning , Tools for
Test Design and Development, Test Execution and Evaluation Tools.

Selection of Testing Tools:

--Match the tool to its appropriate use
--Select the tool to its appropriate SDLC phase
--Select the tool to the skill of the tester
--Select a tool which is affordable
--Determine how many tools are required for testing the system
--Select the tool after having the schedule of testing

Cost incurred in Testing Tools:

 Automated Script Development
 Training is required
 Configuration Management
 Learning Curve for the Tools
 Testing Tools can be Intrusive
 Multiple Tools are required

Guidelines for Automated Testing:

 Consider building a tool instead of buying one if possible
 Test the tool on an application prototype
 Not all the tests should be automated:
 Select the tools according to Organization needs
 Use proven test-script development techniques
 Automate the regression tests whenever feasible

Overview of Some Commercial Testing Tools

 Mercury Interactive’s WinRunner
 Segue Software’s SilkTest
 IBM Rational SQA Robot
 Mercury Interactive’s LoadRunner
 Apache’s JMeter
 Mercury Interactive’s TestDirector
Test Automation using Selenium Tool
1. Introduction to Selenium:
 Selenium is a free and open-source automated testing framework.
 Used for validating web applications across various browsers and platforms.
 Supports multiple programming languages such as Java, C#, Python, etc.
 Testing conducted with Selenium is known as Selenium Testing.
2. Key Features of Selenium:
 Open source and portable web testing framework.
 Selenium IDE for playback and record features without scripting.
 Leading cloud-based testing platform with an easy-to-use interface.
 Supports various operating systems, browsers, and programming languages.
 Languages: C#, Java, Perl, PHP, Python, Ruby.
 Browsers: Internet Explorer, Mozilla Firefox, Google Chrome, Safari.
 Parallel test execution for increased efficiency.
 Integration with tools like Maven, Jenkins, Docker, Ant, and Maven.
3. Selenium WebDriver:
 Browser-based driver for accessing and launching different browsers.
 Supports various frameworks derived from Selenium, such as Protractor,
WebDriverIO, CodeceptJS.
4. Selenium Grid:
 Hub-and-node architecture for parallel testing across different browsers.
 Enables simultaneous testing to reduce time and increase efficiency.
5. Selenium Testing Tools:
 Selenium is a suite of software with different components:
1. Selenium Integrated Development Environment (IDE)
2. Selenium Remote Control (Now Deprecated)
3. WebDriver
4. Selenium Grid
6. Selenium IDE:
Free browser plugin for recording, editing, debugging, and replaying functional tests.
7. Selenium Remote Control (Deprecated):
- Formerly used for continuous testing in conjunction with WebDriver API.
- Selenium 2.0 introduced to support dynamic web pages and Ajax.
8. Selenium WebDriver:
- Browser-based driver for accessing and launching different browsers.
Supports various frameworks derived from Selenium, such as Protractor, WebDriverIO,
CodeceptJS.
9. Selenium Grid:
- Hub-and-node architecture for parallel testing across different browsers.
- Enables simultaneous testing to reduce time and increase efficiency.
 5.14 Object Oriented Testing:
1.Conventional Testing and OOT:
 Difference in unit testing for conventional and object-oriented software.
 Arises from the nature of classes and objects.
2.Object-Oriented Testing and Maintenance Problems:
 Challenges in understanding, testing, and maintaining object-oriented (OO)
software.
 Problems identified by David et al:
 Understanding problem (Encapsulation and information hiding)
 Dependency problem (Complex relationships like inheritance, aggregation)
 State behavior problem (Operation effects depend on object state)
3.Issues in OO Testing:
 Basic unit for testing
 Implications of inheritance
 Polymorphism
 White-box testing
 Black-box testing
 Integration strategies
4.Strategy and Tactics of Testing OOS:
 Verification and validation activities in procedural software.
 Tactics differ based on the structure of object-oriented software.
 Four levels of testing: Method-level, Class-level, Cluster-level, System-level.
5.Verification of OOS:
 Verification process in analysis and design steps.
 Verification of Object-Oriented Analysis (OOA) and Object-Oriented Design
(OOD) models.
 Verification points for models.
6.Validation Activities:

 Unit/Class Testing: Unit testing at the class level.

 Challenges in testing a class: Indirect testing, testing methods, testing inheritance.
 Feature-based testing of classes: Create, Destroy, Modifiers, Predicates, Selectors,
Iterators.

Challenges in Testing for Web-Based Software:

1. Diversity and Complexity:
- *Description:* Web applications interact with numerous components running on diverse
hardware and software platforms.
- *Challenges:* Managing the complexity of interactions, ensuring compatibility across
diverse environments.
2. Dynamic Environment:
- *Description:* The dynamic nature of web software poses challenges in analysis, testing,
and maintenance.
- *Challenges:* Adapting to frequent changes, ensuring stability in dynamic conditions.
3. Very Short Development Time:
- *Description:* Clients of web-based systems often demand rapid development compared
to other software systems.
- *Challenges:* Meeting tight deadlines, maintaining quality under time constraints.
4. Continuous Evolution:
- *Description:* Web-based systems face an ongoing demand for more functionality and
capacity even after deployment.
- *Challenges:* Addressing scalability issues, accommodating continuous evolution, and
ensuring sustained performance.
5. Compatibility & Interoperability:
- *Description:* Web applications are susceptible to factors causing compatibility and
interoperability issues.
- *Challenges:* Ensuring seamless operation across different browsers, devices, and
platforms, resolving compatibility issues.