Testing is a vital part of software development, since it is about finding the software bugs. You can choose from automated and manual testing. Automated testing is good for large projects with many systems users, while manual testing is good for smaller projects or for companies with insufficient budget.
You can also run Continuous testing. The purpose of Continuous testing and continuous integration is to enable continuous delivery, the end goal of which is to accelerate the delivery of high quality software.
Automation is essential for Continuous Testing but Automated Testing is not the same as Continuous Testing.
Try Jenkins Test Automation with codeBeamer ALM. Jenkins is an open source continuous integration tool written in Java. Jenkins provides continuous integration services for software development.
2. 2
Agenda
1. Intland Software
2. Automated vs. Manual Testing
3. Continuous Testing & Automated Testing
4. Automated Testing with Jenkins
5. Live Demo
3. 3
Intland Software
Webinar information
• Demonstration will be followed by a Q&A
session
• Webinar recording will be available at
http://intland.com/webinars/
• Sign up for our upcoming webinars
4. 4
o Founded in 1998
o Headquarters in Stuttgart, Germany
o Office in Silicon Valley, USA
o Our ALM solution includes:
• Requirements Management
• Software Development Management
• QA & Test Management
• Demand Management
• IT Operations (DevOps)
Introduction
Intland Software
6. 6
Automated Testing vs. Manual Testing
Jenkins Test Automation with codeBeamer ALM
Large projects Smaller projects
Many system users Insufficient budget
Sufficient budget Testers are the software developers
Automated testing tool
Testing is a vital part of software development, since it is about finding the software bugs.
7. 7
Jenkins Test Automation with codeBeamer ALM
Continuous Testing & Automated Testing
The purpose of Continuous testing and continuous integration is to
enable continuous delivery, the end goal of which is to accelerate the
delivery of high quality software.
Automation is essential for Continuous Testing but Automated Testing
is not the same as Continuous Testing.
8. 8
Jenkins Test Automation with codeBeamer ALM
Continuous Testing & Automated Testing
Some differences between Automated and Continuous Testing:
• With automated testing, a test failure may indicate anything from a critical issue to a
violation of standard. With continuous testing, a test failure always indicates a critical
business risk.
• With continuous testing, a test failure is addressed via a clear workflow for prioritizing
defects vs. business risks and addressing the most critical ones first.
• With continuous testing, each time a risk is identified, there is a process for exposing all
similar defects that might already have been introduced, as well as preventing this same
problem from recurring in the future.
9. 9
Jenkins Test Automation with codeBeamer ALM
Value and Downside of Automated Testing
• Saving time and catching bugs before release
• Faster feedback on changes
• Lower test expenses
• Improve test reliability
The Value of Automated Testing
Downside of Automated Testing: Increase in up-front investment
• Writing automated tests will take approx. 30% more time
• Poorly designed test suite and re-testing expenses
• Unreliable tests come with additional expenses
10. 10
Jenkins Test Automation with codeBeamer ALM
What is Jenkins?
• Jenkins is an open source continuous integration tool written in Java.
• Jenkins provides continuous integration services for software development.
• Plugins have been released for Jenkins that extend its use to projects written in languages
other than Java.
• Plugins are available for integrating Jenkins with most version control systems and big
databases. Many build tools are supported via their respective plugins.
• Plugins can also change the way Jenkins looks or add new functionality.
11. 11
Jenkins Test Automation with codeBeamer ALM
Automated Testing with Jenkins
• codeBeamer’s Jenkins plugin is a plugin into Jenkins to allow communication and
integration with codeBeamer servers.
• This project is available as open source on codeBeamer server cbci.
• The codebeamer-result-trend-updater Jenkins plugin is available through the Jenkins
plugin manager.
• The codeBeamer-result-trend-updater Jenkins plugin updates wiki pages in codeBeamer
with test or performance results, and build information like source code changes and build
times.
• codeBeamer also provides two wiki plugins to visualise the build information on charts.