Test Magazine – specifically created as a voice for the modern-day software professional and always aiming to give a true reflection of the issues affecting this import market – has compiled a list of software testing providers, of which we are honored to be a part.
In this one-hour web seminar the presenters will explore real-world examples of highly tested products – Mozilla and Xbox – that serve as telescopes into the continuing evolution of test practices: agile testing, requirements-based testing, testing as a service, and crowdsource testing.
Join the presenters for this web seminar to be held on August 21, 2014, at 2:00 p.m. EST addressing notable testing challenges and potential solutions including:
- Lack of mature testing tools for new technologies and practices
- Test automation challenges that continue to plague the industry
- Failure to address security testing needs
- Performance and load testing late in development – or worse, in production
Celtic Testing Experts mission is to use our people, process, and tools to deliver 'Zero Critical Defects' on client Projects.
Based in Atlanta, Celtic Testing Experts (CTE) serves as a long-term software QA partner to some of the world's largest companies. For nearly 10 years, CTE has maintained a 100 percent success rate helping clients deliver quality, cost-effective software on time. The company’s first product, Foresight™, is a unique web and mobile-based reporting tool, making CTE's services the most comprehensive and metrics-driven in the industry.
Ranorex 5.1.1 General changes/Features
- Added support for Firefox 31
- Added support for ARM64 compiled iOS apps
- Removed the requirement to link the MediaPlayerFramework for instrumenting iOS apps
- Further improved mobile web elements to make attribute values similar to those of desktop web elements
- Links shown in test case descriptions of a report are now opened in a separate browser window
Download latest Ranorex version here.
(You can find a direct download link for the latest Ranorex version on the Ranorex Studio start page.)
Ranorex 5.0.4 General changes/Features
- Added support for Firefox 31
Sometimes it is necessary to access the value of a specific variable in more than only one module in a test case.
An example for this would be any kind of converter: In one module the value to be converted is read in. In another module this value is converted. Needless to say, in the converting module the value from the previous module should be used.
This blog post will show how to do this step-by-step.
- The Structure of the Ranorex Solution
- Step 1: Creating a Variable in Module 1
- Step 2: Creating a Variable in Module 2
- Step 3: Connecting Variables in different Modules to one Parameter
- Testing the Solution
As you can see in the screenshot above, the solution “Converter” created for demonstration purposes consists of four different modules. Two variables (varTemperatureCelsius and varTemperatureFahrenheit) should be shared between the modules “GetValue” and “ConvertValue”. The temperatures are read from a weather-website in the “GetValue”-module.
In the “ConvertValue”-module the Celsius-temperature is converted from Celsius to Fahrenheit using another website and compared to the Fahrenheit-temperature from the first website. The whole example is available for download here.
At the beginning an “Open Browser”-action is recorded in the first module. Then a new “Get Value”-action in the second module “GetValue” is added.
Note: Before initializing a new variable, a repository item representing the UI element that displays the temperature needs to be created. This can be done by using the “Track”-button in the Ranorex Repository or by using the Ranorex Spy.
The value of the current temperature is stored in a variable. It is going to be created by clicking on the drop-down menu below the heading “Variable” and choosing the option “As new variable…”.
A context menu will be opened which should look like this:
Here the desired name of the variable and (optionally) a default value can be defined.
Note: The default value is used if modules are running separately and not from the test suite view. It will also be used if a variable is unbound and the test is started from the test suite.
Afterwards the repository item representing the value on the website and the attribute of the “Get Value”-action should access are chosen. The attribute holding the given temperature value is “InnerText”.
This step needs to be done for both Celsius and Fahrenheit values. In the upper right corner of the website the unit of the temperature can be changed.
At the end of the first step the “GetValue” module should look like this:
Note: The temperature value should not be used as identification criteria! The test will only work if the temperature is the same as when it had initially been identified. This can easily be changed by using the Path Editor in Ranorex Spy: Uncheck the “innertext” attribute and check a different appropriate attribute, e.g. “class”.
The step of creating a new variable needs to be repeated for every module the value from the first module should be used in. Here it is the module “ConvertValue” where a value is going to be converted from Celsius to Fahrenheit.
Firstly, the value from the previous module is used for the Celsius text field on the mentioned website. After that the result is validated in a user code action.
After recording and creating the needed variable, the module should look similar to this:
Note: For identification purposes, it would be easier if variables belonging together have the same name. However, this is only a recommendation and not a requirement.
In order to connect all needed variables to each other, a parameter needs to be created.
This is done by right-clicking the test case in the test suite view and clicking “Data Binding” in the context menu.
The test case properties pane will be opened:
Here it is necessary to add two rows in the “Parameters”- section of the window – one for each shared variable.
By clicking the drop down menu “Module Variable”, the variables associated with this parameter (“varTemperature(GetValue)” and “varTemperature(Convert Value)”) can be checked.
Finally, the test suite should look like this:
Now it is time to test the solution. This can be done by pressing “Run” in the test suite.
Note: If “Play” is clicked in one of the modules, the variables won’t be bound. In this case the default values of the variables are used.
The report file should look like this:
In this blog post you learned how to share variables from one module to another. There is one main concept which is always the same for every new module added to the test suite: Firstly a new variable in this specific module is created and then it is connected to a parameter of a test case.
Note: If a variable needs to be shared across test cases, it is almost the same procedure. The only difference is that a global parameter or a parameter in a parent test case is taken. A global parameter can be created in the test suite properties pane.
If something was unclear in this blog post, feel free to ask in the comment section or have a look at the following chapters in our user guide:
- Lesson 4: Ranorex Test Suite
- Lesson 5: Ranorex Recorder
- Lesson 6: UI Mapping with Ranorex Repository
- Lesson 9: Ranorex Spy
Get firsthand training with Ranorex professionals and learn how to get the most out of Ranorex Studio at one of these workshops.
Look at the schedules for additional workshops in the next few months.
This latest release extends the Ranorex mobile web testing capabilities with Android web testing. This enables not only cross platform web test automation, but also increases object recognition for hybrid apps. In addition, the new version allows accessing SMS text messages, battery level, CPU and memory states for mobile devices. General enhancements in terms of unique identification capabilities for Android controls, support for dynamic actions on custom mobile controls and general reporting enhancements have been added as well.
To protect Chrome users from malicious extensions, Google will only allow extensions to the Chrome browser through the Chrome Web Store. With Ranorex 5.1 we have switched to a new Ranorex Chrome Web Store extension and finally to deliver continued full test automation support for Google Chrome while keeping pace with Google’s long term strategy.
For an overview of all the new features, check out the release notes.
Upgrade for free with your valid subscription (You can find a direct download link for the latest version of Ranorex on the Ranorex Studio start page.)
Testing Mobile Web Pages on Android and iOS Ranorex now supports testing of web applications for the Android platform, enabling cross platform web automation for desktop browsers, iOS and Android devices. Setup a single Ranorex web test to execute it on multiple devices and platforms!
Mobile Non-UI Testing While testing the functionality of your mobile application it is often required to double check the performance of a device. It is now possible to perform non-UI tests by invoking technology dependent actions. You can access device specific information like battery, memory or CPU state, or access all of the SMS text messages or calls stored on the device.
Dynamic Actions on Custom Mobile Controls Dynamic actions on custom mobile controls can now be accessed using Ranorex. This means you can now call methods and get and set member variables for your custom Android and iOS controls.
Ranorex in the Chrome Web Store Detaching the Ranorex Chrome extension from the Ranorex setup and adding it to the Chrome Web Store makes it independent of a Ranorex release. Every time Google Chrome has an update, you don’t have to update Ranorex anymore – you simply can update the extension via the Chrome Web Store.
Reporting Enhancements With this Ranorex release, the reporting engine allows you to add HTML descriptions to a report file. Additionally, the success of a test run (i.e. fail or pass) can now be added to the filename of a report file.
Our expert trainers will show you how to create efficient and effective test automation solutions through a combination of theory, tool demonstration and hands-on lab exercises.
Look at the schedules for additional workshops in the next few months.
We look forward to seeing you in one of our training classes soon!