​Applications nowadays have different ways to approach. For example, your application comes in the following flavors.

• Thin-client browser,
• Thick-client application,
• Command-line interface,
• Mobile clients, iOS, and Android.
  
  

Through these different clients, you can do similar things. For example, you can create a record. However, from the server point of view, you do the same operation. Now, you want to test that same function on different clients or, in jargon words, you want to do multi-channel testing. 

I am excited to say that we have recently released version 9.1.0.1 of our Testing Portfolio which contains a number of features and fixes that you won’t want to miss. Here are the highlights but you can find more details in our release notes. 

One of the areas we have been working on is standardization across the portfolio of products, with a view to ensuring that common integrations exist for all of the products and not just some of them.

During conversations with clients, Al Wagner and I often hear some false statements, what we call myths about continuous testing. A few of these myths are “Continuous Testing is just another kind of DevOps flavor”, and “Continuous Testing is just about running test scripts”.
 
We know these statements are not true. Continuous Testing is much more and is a critical part of DevOps, so much so that knowing what it is and practicing it can really impact your bottom line. ​