Scribd
Upload
17 views

Chapter 6

Uploaded by

Radwa atef
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
17 views

Chapter 6

Uploaded by

Radwa atef
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

Chapter 6

Tool Support for Testing

Management tools Static testing tools Test design and


implementation tools
increase the test process support the tester in facilitate generation of test
efficiency by facilitating performing reviews and cases, test data and test
management of the SDLC, static analysis Procedures
requirements, tests,
defects, configuration
Example : Find Bugs, Plant Example : Test Rail , Test Link
Example :JIRA , trello
Azure
Test execution and Non-functional
coverage tools testing tools Dev Ops tools
facilitate automated test allow the tester to perform support the Dev Ops delivery
execution and coverage non-functional testing that is pipeline, workflow tracking,
difficult or impossible to automated build process(es),
Measurement
perform manual CI/CD

Example : Selenium , Junit , Example : Apache J meter , Example :Jenkins , Circle CI ,


Test NG Load Runner Travis CI
Collaboration tool& Tools supporting scalability
• facilitate communication • virtual machines,
• Containerization tools

• Example : Slack , Microsoft • Example : Docker


Teams
Benefits and Risks of Test Automation
Potential benefits of using test automation include:

1. Time saved by reducing repetitive manual work (e.g., execute regression tests, re-enter
the same
2. test data, compare expected results vs actual results, and check against coding
standards)
3. Prevention of simple human errors through greater consistency and repeatability (e.g.,
tests are
4. consistently derived from requirements, test data is created in a systematic manner, and
tests are
5. executed by a tool in the same order with the same frequency) More objective
assessment (e.g., coverage) and providing measures that are too complicated for
6. humans to derive
7. Easier access to information about testing to support test management and test
reporting (e.g., statistics, graphs, and aggregated data about test progress, defect rates,
and test execution duration)
8. • Reduced test execution times to provide earlier defect detection, faster feedback and
faster time to market
9. • More time for testers to design new, deeper and more effective tests
Potential risks of using test automation include:
1. Unrealistic expectations about the benefits of a tool (including functionality and ease of
use).
2. Inaccurate estimations of time, costs, effort required to introduce a tool, maintain test
scripts and change the existing manual test process.
3. Using a test tool when manual testing is more appropriate.
4. Relying on a tool too much, e.g., ignoring the need of human critical thinking.
5. The dependency on the tool vendor which may go out of business, retire the tool, sell the
tool to a different vendor or provide poor support (e.g., responses to queries, upgrades,
and defect fixes).
6. Using an open-source software which may be abandoned, meaning that no further
updates are
7. available, or its internal components may require quite frequent updates as a further
development.
8. The automation tool is not compatible with the development platform.
9. Choosing an unsuitable tool that did not comply with the regulatory requirements and/or
safety standards.

You might also like