How many hours a day do you spend making sure that your website looks and works as expected? Fact is that a website or web application is a determining factor for your online success, and its quality is defined by its functionality across all browsers and operating systems. But web testing can be a challenging task, and it’s easy to make mistakes.
We wanted to create a product that simplifies the way web testing is done, while at the same time making it more efficient. We are incredibly proud to finally announce the release of Ranorex Online beta! Compared to Ranorex Studio, this new web testing service focuses on the essentials of automated web testing, and provides the fastest and easiest way to improve the quality of your web presence in real browsers.
You can instantly start testing with Ranorex Online. This is the only web testing service that doesn’t require an extension or plug-in. Simply register for a free account on our Ranorex Online website to immediately test your website in real browsers. No matter where you are. No matter which operating system or desktop browser you use. The icing on the cake: it’s free-to-use.As easy as surfing the web
Test your website the way your users will experience it. You don’t even have to code. The intuitive recorder makes website testing a blast and you’ll get instant feedback. Go to ranorex.io and enter the URL of the website you want to test to instantly move to recording mode. Click around, hover over elements, select items, fill out forms or walk through the entire online check-out process. Every action is immediately recorded. Curious how it works? Check out the examples on our website!Prepare your website for success
Free up hours of your day! We all know that the only way to make sure that your website always works and looks as expected is to test it in all possible environments. Ranorex Online offers an easy way to automate web testing. You have recorded a workflow on your website in Safari on macOS? Simply use the Play-Link of the recording to replay it across popular desktop browsers and operating systems. Chrome, Firefox, Edge, IE and Safari – now you can test it all with just one recording. It’s time to take the fast and easy route to improved website quality!Make website testing a team effort
Capturing errors in all detail is difficult and reproducing them even more so. Now you can keep team members in sync and give feedback the way it is really needed. You want to show your colleague a problem you have found in your web application? Simply record it and share the Play-Link of the recording, even if she doesn’t have a Ranorex Online account.
Ranorex Online is a software as a service. Based on your feedback, we’re constantly adding new features and functionalities, to make your testing experience even smoother and more efficient. We can’t wait to see what you think of it!
Do you want to transition from waterfall to agile? Like so many other companies, you may also seek to replace waterfall with agile in a quest to shorten the time-to-market and deliver high-quality software faster, more frequently and at a lower cost. The road to agile, however, can be a rocky one. That’s why we have put together a few lessons and tips that will help you in succeeding in agile software development.# 1: Embrace the change in mindset and culture.
More than anything, agile requires a change in mindset and culture throughout the entire company. The key to success is that everyone involved knows what to expect, is patient and, most importantly, embraces change. Agile is about adjusting. It’s about continuously assessing if requirements and goals are still valid. This new learning culture is a big challenge.# 2: Make the transition to agile a joint company process.
You won’t be able to reap the rewards of agile without engaging both the management and the team. If not everyone involved is committed and participates effectively, you’ll unavoidably run into problems. That’s why you have to make sure that the transition to agile is a joint activity. Communication, effective contribution by everyone involved and continuous planning is required to get all interest groups on board, and avoid tension between how the teams operate and how management runs the company.# 3: Roles and responsibilities change throughout the company.
Undoubtedly, the shift to agile affects roles and responsibilities within a company. A top-down command-and-control culture should be replaced with horizontal conversations. Management helps to remove impediments, encourages teams and ensures the business alignment of projects. It has become a facilitator and is in charge of creating an environment in which teams can grow. The team itself is a group of experts, who know best themselves what should be done by who and how. They are self-organizing and self-reliant.# 4: Encourage transparency and exchange between teams.
In an agile environment, small teams that communicate and work together efficiently are important. Consequently, transparency is key to success. Be open about failures, discuss impediments and work on a solution together. This will create unity in the team and build towards a better product. At the same time, you need to encourage exchange between those highly productive units so as to avoid isolation of individual teams.# 5: Agile is not a linear process.
In waterfall projects, teams were used to working in a sequential manner: requirements, design, implementation, then testing and maintenance. Everything was strictly planned and scheduled. In contrast, software is developed and delivered in small chunks in agile. To ensure it meets actual market needs, the software is continuously adjusted according to changing requirements as well as to feedback from customers and stakeholders. Business managers, developers and testers have to work together closely and stay in sync to evaluate the situation and determine the right next steps.# 6: The team is responsible for quality.
The team needs to collaborate right from the beginning: when it comes to defining requirements, the scope of projects and what is needed to assure the quality of the software. As software quality is a continuous process that requires commitment from everyone involved, the whole team is in charge of testing.# 7: Test early and often.
As software is developed incrementally, code is constantly changing. Every time you check in new code, you have to ensure that it meets its requirements and does not break existing functionality. The frequency of code commitment requires fast feedback from tests that can only be achieved with automation. When you integrate tests into your continuous integration process, each code change is automatically tested. The goal is a near real-time feedback, which helps you in reacting to potential errors as soon as possible.# 8: Automation is a necessity, not a necessary evil in agile software development.
Agile software development will not succeed without test automation. Manual testing is slow, labor intensive, inconsistent and prone to errors. If you want to reduce the time-to market and release small increments of software in frequent iterations, agile test automation has to be an integral part of the project from the beginning. Well-designed automated tests are faster, provide continuous feedback on software quality, increase risk-coverage and will give you confidence in your application.# 9: Early feedback from automated tests is important.
The earlier you find bugs in your software, the easier and cheaper they are to fix. The key is to understand what to automate and when, in order to get quality feedback from your automated tests. If you want to get early feedback on the quality of your code, you need to shift testing left and perform more automated testing on a unit and mid-tier level. The iterative feedback increases transparency and enables you to react to potential problems faster, decreasing the risk of release delays and software failure.# 10: Test automation tools have to enable team collaboration.
In agile software development, it’s all about continuous testing and team collaboration on agile test automation projects. When you choose a test automation tool for your team, make sure that it fosters this collaborative dynamic in cross-functional teams, enables you to start with test automation early in the development cycle, supports reusability of tests and encourages communication and feedback. Always keep in mind that after all, your team is one of your greatest assets.
We’re excited to announce that Ranorex 6.2 is ready for you to download! In this release, we’ve focused on providing you with an advanced technology support for desktop and mobile applications as well as on making it easier for teams with mixed skills to collaborate on test automation projects.Advanced Technology Support
We’ve made the support of innovative technologies a priority and now enable testing of Chromium-based frameworks in desktop apps and WKWebView objects in iOS apps.Chromium Embedded Framework (CEF) support
CEF is one of the most frequently used frameworks for embedding web content in desktop applications. Next to Google’s native CEF implementation, we now also support testing of these Chromium-based frameworks:
- Qt WebEngine
The WKWebView class enables you to embed interactive web content in your iOS mobile applications. Using Ranorex 6.2, you can now test your embedded WKWebView objects.User Code Library
Sometimes, you need to add further functionality to your tests with user code. We understand that in a team with mixed skills, not everyone wants to code. That’s why we’ve introduced the user code library with Ranorex 6.2. It gives you direct access to the user code methods your colleagues have previously created in a test automation solution, so you can add additional functionality to your tests without writing a single line of code.A quick overview of the workflow:
If you’re a developer or tester with programming skills, you can start by filling the user code library with user code methods. You can logically organize methods that relate to a specific workflow or application area. A tip: Add a description to each method. This makes it easier for your colleagues to find the right user code method .
As a tester in your team, you can directly access the library from the action table and select a method from there to use it as an action. This way, you can add further functionality to your tests without having to dip into code!
We hope you have as much fun using this update as we’ve had creating it!