cross browser testing



We work hard to improve the functionality and usability of our autonomous testing platform, constantly adding new features. Our sprints are weekly with minor updates being released sometimes every day, so a lot is added over the course of a month. We share updates by email and social media but wanted to provide a monthly recap of the month’s latests enhancements, summarizing the big and small things we delivered to improve your success with the Testim.

Test Reruns

What is it?

An easy and fast way to rerun a test with the exact parameters used in another run.

Why should I care?

When running large suites, many times you want to rerun a smaller subset of those tests that failed. Since tests fail for a number of reasons, this new capability allows you to test temporary errors or fixes. Reruns let you run a test with the same parameters as a previous test run with a click of a button. This will include all dynamic parameters, from the CLI, Test Data, and parameters exported from tests that ran before this one (via exportsGlobal). Learn more

test suite rerun

To Reuse or not to Reuse

What is is?

Reusing actions is one of the basic principles of programming. Testim always supported reuse, and now we push toward even more developer best practices. For every new group, API call, or custom code step that you create, Testim will prompt you for a (meaningful) name, and whether you would like to make this step shareable or not.

Why should I care?

This feature will save you time since you can author the test once and call it to be used in any suite of tests. This makes it faster to author tests when making changes to a shared group, but do not want it to affect other tests in the suite. You can find more information on Reuse in our docs

test reuse

Mobile Web

What is it?
Testim now supports the authoring and execution of tests for mobile web.

Why should I care?  
The number of mobile devices has suppressed the number of desktop computers. We all consume content through our mobile devices and users expect your application to provide superior experience regardless of the medium. Responsive websites look and behave differently than desktop hence require different tests. Learn more

mobile web

Customers have access to these features now. Check it out and let us know what you think. If you’re not a customer, sign up for a free trial to experience autonomous testing. We’d love to hear what you think of the new features. Please share your thoughts on Twitter or Facebook.

We work hard to improve the functionality and usability of our platform, constantly adding new features. Our sprints are weekly with minor updates being released sometimes every day, so a lot is added over the course of a month. We share updates by email and social media but wanted to provide a recap of the latest enhancements, summarizing the big and small things we delivered to improve your success with the product. We’d love to hear your feedback.

Test History

Is past performance an indicator of future success? The folks on Wall Street don’t think so… But we do! This is why we are pleased to offer the new Test History feature in Testim.  

The new Test History feature allows users to see slide and dice test results to get more actionable insights.

Why should I care?
This gives users much more insight from the test results. Quickly analyze how many tests ran during the selected time frame, how many succeeded and the average duration of each run, how your tests performs across multiple environments and whether certain environments or scenarios consistently fail. This allows project team to see improvement trends across scenarios or environments over time. Click here to learn more.

What’s included?
Test History allows you to filter based on the following parameters:

  • Run time
  • Specific tests / All tests
  • Last X runs
  • Status
  • Browser

Create Dependencies Between Tests
This new capability allows users to create different aspects of dependencies between tests. As a best practice, we recommend to keep the tests as isolated as possible. However we recognize that sometimes you need the ability to create dependencies between tests.

Why should I care?
Now users can create a logical sequence of tests. By working closely with our customers, we’ve seen project teams required to set a sequence of activities. A general testing framework does not allow you to create a sequence, forcing users to create one long test which may result in performance issues and failures. By creating dependencies during test plans you can create shorter discrete actions, order them in sequence and set dependencies and share data between tests. Click here to learn more.

Setting up Cookies
Cookies is a reserved parameter name for specifying a set of cookies you would like Testim to set for your application.  You can set cookies for each browser session before the test is started or before the page is even loaded. Use cookies to set browser data to be available for your tests. The cookies parameter is set as an array, where each cookie object needs to contain a name and value properties.

Why should I care?
Websites use cookies to personalize user experience. By using this feature, you can test different types of personalized experiences. Click here to learn more.

Improved Scrolling
More flexible way of scrolling through your page.

Why should I care?
Traditionally scrolling in your test automation would be set by pixels so you would test your script to skip 60 pixels. Offering a more flexible scrolling ability makes your tests more adaptive. An  example is to scroll to the element, mouse wheel. Click here to learn more.

How do I get my hands on these hot new features?
Customers have access to these feature now, check it out and let us know what you think. If you’re not a customer, test drive the new features by signing up for a free trial to experience code and maintenance free test automation.

Testing is one of the key processes in software development. As the requirements to support multiple browsers and devices increases, it is driving the demand to automate the functional testing of applications. While teams embark on their DevOps transformational journeys, the handoffs between traditional application lifecycle silos begin to dismantle, enabling a continuous process of updating their applications.

The key challenges for software teams in DevOps include:

  • how to achieve maximum coverage testing with shorter time frames?
  • how to figure out what to automate vs. leave manual?
  • how to transform from testing and validation before go live to more predictive forms of testing and real-time quality monitoring?

With the increased adoption of agile methodologies, test automation is a key piece of continuous testing. According to the 2015-2016 World Quality Report, research show that the average percentage of test case automation has increased from 28% to 45%. An enabler of this trend has been the advancements in development and testing tools which have helped organizations build a solid infrastructure for automation.

Testim’s stable, self-healing, end-to-end test automation solution is recognized by Software Testing Help as a Top 20 Best Tool to help developers and/or testers create their test suites without any coding, script management or maintenance of the tests. Using machine learning, Testim provides the maximum coverage with the fewest amount of test scenarios allowing teams to optimize their test suite. This also eliminates the need of trying to figure out what to automate vs. leave manual since tests are automatically created as the user uses the application. Additionally, Testim helps teams transform from testing and validation by leveraging historical data to prioritize tests.

“We are humbled by making this list,” says Oren Rubin, CEO for Testim. “This is a testament to our commitment to helping project teams eliminate the complexity of building their test automation suite.”

About SoftwaretestingHelp.com
STH is one of the most popular blogs focusing on Software Testing and Quality Assurance topics. This blog is growing up so fast and currently, we have around thousands of testing professionals who visit every day and gain help from this blog. The topics which we cover on this blog include – software testing tutorials, methodologies, manual testing, automation testing, testing tools, interview questions, web testing, testing templates, quality assurance, testing certifications, books, career guidance, job openings, latest testing trends, news, and much more that cannot be listed here on a single page.

About Testim.io
Testim.io leverages machine learning for the authoring, execution and maintenance of automated test cases. We use dynamic locators and learn with every execution. The outcome is super fast authoring and stable tests that learn, thus eliminating the need to continually maintain tests with every code change. Netapp, Verizon Wireless, Wix.com and others run over 300,000 tests using Testim.io every month.

In a world gone mad, where customers will access your application through any damn browser they want, how can you meet their expectations that your app will work perfectly whether it’s running on their phone, their laptop, their tablet, or even their internet enabled refrigerator? Cross-browser testing is essential to ensuring your customer has a consistent user experience, no matter how they access your app. But is just not realistic to manually test all the potential combinations of browsers and systems out there.

However, over the last few years there are a number of vendors who have developed different approaches to cross-browser testing. We have assembled a short list of the 12 most interesting. Each has a slightly different set of capabilities, and a different price level too. Some support mobile, some don’t. Some have security built in, and some do not. Selenium support varies as well.

Most, like Testim.io, have free trials, so you can evaluate which one is the right solution for you.

How to Choose a Provider

There are a number of attributes you should consider when choosing a grid provider. These include:

  • Coverage of browsers, versions and operating systems.
  • Stability – a flaky grid will result in test failure, leading to running those tests again at best and developers spending time figuring out why the test failed at worse. A flaky grid will result in valuable time being lost.
  • Enterprise grade – If your app is internal to the organization you will need tunneling and potentially VPN, encryption or other other security requirements as mandated by your CISO. Not all cross browser testing providers support that.
  • Integration – No organization will change its tool-set due to a grid. Your team is likely using Git, Jira, Slack, Jenkins and/or other tools. Integrating into those tools to trigger your tests and read through the results is essential. Without it, you’ll either have to change the process or end up spending your budget on a tool that will be useless.
  • Features – Do you need screenshots? Single sign-on?
  • Mobile – If you are looking to test your mobile app or web you need to decide whether you settle for emulators or need real devices. Then you have to analyze the variety of devices being offered, including geographies, mobile operators, OS versions etc. Many times you have to drill down to the set of actions the grid supports. Does your app use location sensors? Camera? Fingerprints? Not all grid providers support these actions.

Capability Grid

Cross browser tools
Cross browser tools – Comparison

Be smart & save time...
Simply automate.

Get Started Free