It is never a dull moment with Inflectra, and after the lull of summer, we are back with vengeance! Which is to say, we are going all out sponsoring two software testing events in September-October 2017 in the US: STPCon in the greater D.C.-area and Agile Open Florida, in Orlando, Florida. So, if you are attending one of these, read what Inflectra has in store for you (and if you are not, there is still time to sign up):(Read More)
As you may know, one of the core strengths of Rapise is its support for testing Microsoft Dynamics applications. Rapise offers the best automated testing solution on the market for Microsoft Dynamics AX, CRM and 365. However that is not sufficient for us, after several customer requests, we are pleased to announce that the next version of Rapise due for release in a couple of weeks will also include built-in out of the box support for MS Dynamics NAV as well.(Read More)
Ever wonder which automated UI testing software to use for Dynamics AX ?
We have big news - Rapise 5.2 is Now Released! Our automation development team has been working to add the remaining features needed for full scriptless test automation using Rapise Visual Language (RVL) and now it is here!(Read More)
Software products are not islands, the value of a product is how well it works with the surrounding ecosystem of other technologies, frameworks and platforms. In this article we highlight some of the recent work by Team Inflectra to integrate our Rapise test automation tool with ElasticSearch and also demonstrating how it can be used to automate a combination of web and desktop UIs to drag and drop files from Windows Explorer to Google Drive.(Read More)
We are busy bees this summer, and one of the most exciting new features of Rapise is the fact that we're adding support for data-driven testing using the new Rapise Visual Language (RVL) with the introduction of Maps and Loops to the new scriptless language.(Read More)
We just released the final evaluation guide in our three part series comparing legacy HP products with new and easy to use alternatives from Inflectra. Coinciding with the announcement that HP is selling its software assets to Micro Focus, we thought it would be good to highlight the three guides in case you need help convincing your boss or a co-worker on the benefits of switching to Inflectra.(Read More)
Web applications are a perfect example of a rapidly moving target for UI test automation tools. Agile and DevOps drive small changes and frequent releases. This leads to certain challenges in QA field. How to create tests that survive after small UI changes? How to create tests that produce same results if ran 10 times in a row on an unmodified application? How to create tests that check exactly those features they were designed to check?
Answers to these questions are not entirely simple. Test automation is still an art.
In this blog we try to figure out what every test automation engineer can do to find the right answers. First I'll give a few examples that illustrate common challenges in Web UI test automation.(Read More)
Take any tool for UI test automation and you will notice that they always lack support for some of the UI controls. And I am not talking about trivial ones like buttons and edit boxes, but the one that are custom controls, which are unique and created for specific needs. It can be some sophisticated grid or menu or a fancy tree. A number of such controls in this rapidly evolving world is growing exponentially. So, every UI test automation engineer is challenged by emerging UI frameworks in every project. This is especially true for Web applications.
As a provider of a UI test automation tool - Rapise - we constantly do our best to arm engineers with the most advanced technologies to help them deal with new UI controls.
This article by Danis Markovtsev will showcase a real-life example of this.(Read More)
We’ve mentioned before that Inflectra is sponsoring DevGeekWeek2017 in Israel later this month. One of the perks of being a sponsor is an ability to engage with the conference attendees through seminars and talks. It is then only natural that we decided to also contribute our experience, technical knowledge and testing wisdom to this conference.
So, we are sending #TeamInflectra’s crème de la crème - Adam Sandman, Inflectra’s Technical Director, to talk about A Real-life TestOps Environment during a seminar called: Real Testing Scenario Strategy lead by Anna Lucovsky on June 21, 2017.(Read More)
In this short blog post, our test automation guru - Denis Markovtsev explains the ideas and principles behind the design of Inflectra's new Rapise Visual Language (RVL) introduced in Rapise 5.1. RVL is a spreadsheet-based approach to UI test automation implemented in Rapise to help domain specialists and test analysts, who are not programmers, participate in test automation projects.
Team Inflectra was excited last week to present at the SQADAYS 21 testing conference in Moscow. Leading practitioners in Software Quality Assurance attended the XXI International Conference of Software Quality Assurance in Moscow, on May 26-27, 2017 to share knowledge on test automation, quality assurance and all things software testing. Our colleagues Denis Markovtsev and Alexey Grinevich attended the event, with Denis speaking on the topic of best practices for testing an application that is constantly being upgraded.(Read More)
We're very excited about the next version of Rapise coming out later this week. It has many enhancements and improvements for testing the web, mobile and desktop applications which we'll be discussing in future blog articles. It also has some nifty new features to make the testing of REST web services even better.(Read More)
Chris, one of Inflectra's latest interns, has created a brand new way to get data into SpiraTeam: Google Sheets (feel free to check out the code on Github). Google Sheets is great product, letting you create spreadsheets from anywhere at anytime. While it's great for us as consumers to use, what's it like for a developer? Chris explains some plusses and minuses to working with the Google Sheets API.(Read More)
We're very excited about the next version of Rapise coming out later this month. It has many enhancements and improvements for testing the web, mobile and desktop applications which we'll be discussing, but the biggest new feature is the ability to create scriptless tests, using a familiar Excel-based grid framework for composing automated tests. Unlike some other tools (cough cough HP UFT) this is natively part of Rapise, not some add-on.(Read More)
One of the most popular sessions in our recent user summits in London, Zürich and Mannheim were the discussions of the future Inflectra product roadmaps. We presented the proposed roadmap for SpiraTest, SpiraPlan, SpiraTeam and Rapise to the community and captured their feedback and suggestions (sadly there was not time to also cover KronoDesk). Based on their feedback we have now published the updated roadmaps for the products for 2017/2018. Learn what users in Europe had to say.(Read More)
As we close out our focus on Rapise this month, we thought it would fun to take a look at how the UI used to look when it was first released in 2010, as well as look at how we've adjusted the UI to include new features while keeping the application simple to navigate.(Read More)
As you may have read, we've just released the latest major update to Rapise, our unified platform for testers. Rapise 5.0 brings many benefits for testing web applications (Edge support), desktop applications (faster testing of WPF and UWP apps), API testing (SOAP support and REST enhancements), and load testing (integration with NeoLoad).
However the biggest piece of news was that we now have added support for Microsoft Dynamics, the powerful ERP and CRM system from Microsoft. We support the current Dynamics AX and CRM platforms as well as the future Azure-based Dynamics 365 service. This article discusses what this means for you and why it is such big news!(Read More)
In the next week or so we shall be formally releasing the next version of our popular automated testing IDE. In this article we give you a taste of what to expect for both existing customers looking to upgrade and new customers that want to empower their testers with powerful tools to make their job easier.(Read More)
The move to cloud computing has highlighted the importance of
Application Programming Interfaces (APIs). With the rise in cloud
applications and interconnect platforms, API testing is a necessity. However what makes a good API? What happens when you change the application but need to support existing users of the API?
As we're wrapping up the final testing of SpiraTeam v5.0 we're adding the documentation and testing the new v5.0 API. This API will be available in both REST and SOAP options. This reminds us of why we're adamant about the need to version the API and not resist the impulse to make changes to existing functions and methods. This article explains discusses API versioning and some suggestions we have for anyone thinking of adding an API to their product.
During our conversations with customers we have found that a common need when using Rapise to test web applications is to be able to easily and quickly match a specific item in a grid/table of results without worrying about the order or position of the item. This article provides a neat new feature added in Rapise 4.0 to make this common task easier.
When companies evaluate test automation tools
for web testing they are often facing a similar question: What's the
advantage of using Rapise
instead of Selenium? Though the larger question is: Why should you pay
for a commercial tool instead of using a free one?
In accordance with the theme this month of user interface updates and user experience in general, we'd like to talk about some of the UI changes being made to our Rapise test automation product. These changes are based on the results of user testing and feedback from our customers. It's an interesting topic because it shows the dramatic impact the UI can have on an application.
As part of our work on Spira v5.0 and the new plugin we're developing for the popular ZenDesk help desk system, we need to be able to make cross-original REST web service calls to Spira. For KronoDesk we used JSONP, but for ZenDesk we decided to add CORS (Cross Origin Resource Sharing) support to Spira 5.0 to make it easier. However implementing CORS support using WCF was not so easy so we're publishing our solution to help other software developers implement CORS using
Do you need to test native mobile applications? Are you looking to test on both physical and simulated devices? Are you tired of manually coding automation scripts and looking for an easier way. This webinar explains how Rapise can simplify the testing of your mobile applications using an Android application and tablet as an example.(Read More)
Many times, when testing, a tester will want the ability to run through many variations of the process recorded. This can be accomplished manually by running the test, then editing the test to use different data. The process of editing, rerunning, lather, rinse, repeat, gets very old after the first time. Plus this process is not very efficient with time and it can introduce issues through the slip of a finger. Enter Data-Driven Testing with the Spreadsheet Object (Read More)
These days APIs are all the rage, with any application or web site worth its salt providing an API, usually using SOAP (more likely nowadays) or REST as the possible option. Well we've had a SOAP API available in Spira since 2008 and recently we announced the introduction of a complete REST API as well. So what does this mean for the future of Spira and why did we choose to add a REST API? (Read More)
In Rapise there are several options as far as controlling interaction with a database from outside the user interface. Most of what you do in Rapise is interaction just like a user would, clicking buttons and interacting with drop-downs, text boxes, and on screen data, but occasionally there is a need to make a manipulation behind the scenes. (Read More)
Once you have learned objects with Rapise, it is time to use them, or modify how you use them. As a primary functional element, buttons are pretty ubiquitous. Submit, Calculate, etc… You push a button for most transactions. This article explains the different operations that can be performed with buttons during automated testing. (Read More)
You built your first test. And it works, as planned! Congratulations! Based on that test you submitted a bug and proved your worth and the value of automation! Again congrats. Now development has “fixed” the bug, time to retest. OOPS! The test fails, not due to the bug, but because the flow is wrong. (Read More)
Rapise is powerful, and flexible. But how? It is not only in the many ways you can learn an object, manipulate an object, or alter the test. Rapise also gives you the ability to select which recognition engine to use. Not only that, you can also modify the engine itself. (Read More)
So lets assume you have read the other articles, and know how to learn objects in Rapise. What do you do now? How do you run and modify a test? The answer depends on the method used to create the test. (Read More)
What happens when all else fails? You use a hammer. In the case of Rapise, that hammer is analog recording.(Read More)
Every now and again, and it does happen to all of us, we encounter an object that may be poorly built, hacked together, incompletely coded, or just resistant to being recognized by any of the myriad of methods employed within Rapise. I would take this situation from two separate perspectives depending on how often you encounter the issue of not being able to learn or interact with an object with Rapise. (Read More)
With our test automation tool - Rapise, you have a powerful and flexible automation engine for your QA projects. One of the reasons it is so powerful is that it is easy to get started and develop your first test, delivering results right away.(Read More)
Rapise has several methods for learning the objects within the application under test. While still easy to learn, this method does not automatically develop a runnable test that will deliver any meaningful results. Herein we will discuss the learning methodology and provide a flow to follow, however we will not have a runnable test in the end as no input or click-stream data will be captured.(Read More)