- Added support for Firefox 35
Download latest Ranorex version here.
(You can find a direct download link for the latest Ranorex version on the Ranorex Studio start page.)
This blog post will explain the term regression testing and how Ranorex test automation can support in doing functional regression testing. Additionally the blog post will confront you with the problem occurring with regression testing including a strategy to overcome it.
When developing software, every modification of or addition to the existing code might lead to an inoperative state or to an error condition within the existing functionality. These side effects caused by code modifications are called regressions. To determine a regression it’s necessary to re-test already existing and tested parts of a program every time the code has changed.
That’s what regression testing is all about.
Regression testing is not done to expose new defects but to verify the functionality of the existing parts of a program. Testing the same parts of a program after every change in code sounds a little boring and time consuming when doing manually – not to say it is impossible when being performed for every build. For this reason it makes sense to automate regression testing using Ranorex Studio as the ROI of automated regression testing is very high.
Even helping yourself with automated regression tests still does nothing about the fact that there is never enough time to run all test cases.
To minimize risks it is absolutely essential to construct subsets of test cases which have to be executed for every build, test cases which should be executed for every build and test cases which could be executed if there is time left.
After designing your test cases it is time to break them down into the following categories:
- Smoke Tests: The test set which should be executed very first. These tests will determine whether the build is even testable. Smoke tests typically cover a wide but shallow range of functionality.
- High Prior Tests: The test set which is executed most often. These tests ensure that the functionality is stable, intended behaviors and capabilities are working, and important negative tests and boundaries are tested.
- Medium Prior Tests: The set in this category will test the given functional areas and features in a more detailed manner. Additional most of functional specifications are examined including boundary, negative and configuration tests.
- Low Prior Tests: The test set which will be executed least often (e.g. check for error messages, stress tests, UI glitches, etc.).
The most important question that arises is how to figure out which test fits in which category. Following the approach described in the blog post “Rapid Test Case Prioritization” provides a smart and fast way to fulfill this mission.
- Categorize all functional verification tests – also known as happy day scenario tests – as high prior tests.
- Categorize all negative, boundary or validation tests as medium prior tests.
- Categorize all non-functional verification tests as low priority tests.
Now you have a rough division into the three categories. The next steps will refine the selection.
- Divide all functional verification tests into high and low important tests
- Categorize all low important functional test as medium prior tests
- Divide all negative and boundary tests into high and low important tests
- Categorize all high important negative and boundary tests as high prior tests
- Divide all non-functional verification tests into high and low important tests
- Categorize all high important non-functional verification tests as medium prior tests
- Repeat the steps above until there will be no more changes
After doing so, the smoke tests have to be identified.
- Divide all high prior tests into critical and important tests
- Categorize all critical tests as smoke tests.
Using Ranorex to automate your regression tests will in any case dramatically increase the efficiency. However you’ve got to think about how to prioritize your test cases and the given approach might help you in successfully implementing this process.
The challenges in automation that testers face often lead to subsequent failures. In the webinar you will learn how to respond to these common challenges by developing a solid business case for increased automation adoption. You'll learn a lot through Jim Trentadue's explanations which cover a variety of automation perceptions and myths.
Register for the free webinar " Why Test Automation Fails " to be held on January 22nd, 2015, at 10:00 AM PST / 01:00 PM EST.
What's the difference between Ranorex and Selenium?
At first it seems that both tools are similar and as such facing the same challenges when automating a web application. However, it is very relevant to understand further aspects when comparing both web test automation tools.
See the tool comparison and the reasons why you should pay for a commercial tool instead of using a free one: Ranorex vs. Selenium
We would like to thank all of our 1700 clients for caring so much about test automation. It's great to see how Ranorex products help them to excel with their automated testing.
Annual ranking of the fastest growing technology companies About Deloitte Technology Fast 500 EMEA
The Deloitte Technology Fast 500 EMEA program is the region's most objective EMEA regional industry ranking focusing on the technology field, recognizing technology companies that have achieved the fastest rates of revenue growth in Europe, the Middle East, and Africa (EMEA) over the past 5 years. Combining technological innovation, entrepreneurship and rapid growth, Fast 500 companies - large and small, public and private - span a variety of industry sectors, and are leaders in hardware, software, telecom, semiconductors, internet, media and life sciences along with emerging areas, such as clean technology.
The input you provided in the survey is invaluable for us because it enables us to take a closer look at our current work and make adjustments and improvements wherever it is necessary.
We value your opinion and would like to thank you again for taking the time to participate in our survey.
You can find the most pertinent data summarized in the following infographic:
Download latest Ranorex version and start YUI testing
Upgrade for free with your valid subscription (You'll find a direct download link to the latest version of Ranorex on the Ranorex Studio start page.)
Challenges in automation which testers face often lead to subsequent failures. Learn how to respond to these common challenges by developing a solid business case for increased automation adoption by engaging manual testers in the testing organization, being technology agnostic, and stabilizing test scripts regardless of applications changes.
Learn Jim Trentadue’s explainations of a variety of automation perceptions and myths:
- The perception of significantly increased time and people to implement automation.
- The myth that once automation is achieved, testers will not be needed.
- The myth that automation scripts will serve all the testing needs for an application.
- The perception that developers and testers can add automation to a project without additional time, resources or training.
- The belief that anyone can implement automation.
Register for the free webinar "Why Test Automation Fails " to be held on December 11, 2014, at 10:00 AM EST / 04:00 PM CET.
The 7th Software Quality Days will take place at the "Austria Trend Hotel Savoyen Vienna" from January 20th to 23rd, 2015 and is aimed at quality assurance professionals, product managers and software testers.
The conference focuses on everything to do with system and software quality. Keynote speeches, practical lectures, expert talks and workshops will present the latest trends and best practices in software quality management along with ideas for improving methods and processes. Interact with software testing experts and learn from presentations provided by industry experts.
Visit our booth and learn more about test automation with Ranorex. See how to make your automated testing more effective and get answers to your questions directly from Ranorex professionals.
Don't miss the German-language session entitled "Ein Web-Test für multiple Plattformen - Design Tips for Testability" on January the 21st (14:00-14:35, Solution Provider Forum) which will be presented by our own Hubert Gasparitz. We look forward to seeing you there!