An Automation Testing Tool to Fail Proof your Product

An Automation Testing Tool to Fail Proof your Product

USD $ 500 million. Microsoft spent this amount to market Windows Vista OS in 2007.

But guess what? The software had so many compatibility & performance issues that even the company’s most loyal customers revolted. And Vista flopped.

Which means that however big a brand you are you, can no longer assume that your customer base will lap up any software you build.

BEFORE you release the product, you need to ensure it works real time by deploying the build on a test or staging environment and further running Performance, regression and compatibility tests on this reliable test automation tool called Test Odyssey to be doubly and triply sure it’s 100% fool proof.

Which is what NASA does.

The Jet Propulsion Laboratory practiced Continuous Delivery (CD) in building software that landed Curiosity rover on Mars. They processed the data it sent back each day, and beamed the next day’s mission plan back upto it!

So how do you get started on this 3 step journey towards Continuous Delivery (CD)?


It’s important to note here that only if you have built Continuous Integration (CI) into your test practice, you can get started on the journey to implement CD.

Simply put, Continuous Integration (CI) is to merge all copies created by your developers to a shared mainline, several times a day.

Detect and fix Integration bugs early; save time and money.

Spend less time debugging and more time in adding new features.

Fast Feedback: no more tense waiting to check if your final code is going to work or not.

You can have the current build handy for testing, demo or release purposes

with cd you can build, test with a new generation test automation tool and release.


Less risk, as you don’t pass failed code to the next stage.

You can get immediate feedback on new features; that way you quickly learn if it’s a hit or a miss.

You can respond fast to fix login errors when the software is accessed from different devices.

Onus of software delivery lies not only with your internal teams but business owners as well.

So what is the difference between Continuous Delivery and Continuous Deployment?

In the former, the pipeline automatically tests the application but keeps the deployment as a manual step. However in the latter case, deployment of the build is automatic with no human intervention.

Test teams can opt for either process.

There are several tools available in the market to support CD. However Jenkins is quite popular and extensively used as it can be used as a CI server or turned into continuos hub for a project. Jenkins can integrate with practically every tool in CI & CD toolschain. It executes both CI & CD and has several advantages over it’s competitors.

It’s Java based & Open Source!

Tracks metadata about builds, including the most recent failed and successful builds

It also builds history and provides console outputA typical Jenkins – workflow is shown below:

Note: You can run this entire set up either on cloud or on local machines.

If you are planning to run this on a cloud set up, you could consider AWS cloud infrastructure; apart from its other benefits, it also has a lot of data security options because it’s:

The first Cloud Service Provider to Adopt New PCI DSS 3.2.

Compliant with other certifications such as SAS 70 Type II, ISO 27001 & FISMA

Network firewalls are built into Amazon VPC and web application firewall capabilities

what it means for your teams is that each time they login into the test automation tool either from office or any other premises; they don’t need to worry about data privacy as AWS has encryption in transit with TLS across all devices.

A typical process flow on AWS cloud looks something like this:

Test Odyssey scores over other test automation tools in the market because it leverages the strengths of both AWS Cloud environment & Jenkins tool as shown in the flow chart below:

Test Odyssey is based on AWS cloud. So if your Test Practice & CI are already on cloud, you can get started with Test Odyssey for CD right away!

To create a plug in that interfaces with the Jenkins tool takes a huge software development effort for any test automation tool.Test Odyssey makes the whole process seamless, as it has already developed the “Test Odyssey Execution Plugin” which speaks to the Jenkins tool; it is readily available for download once you subscribe for the tool!

The Test Odyssey execution plug in works equally well across regardless of the fact if your test practice is located on cloud or on a non – cloud environment.

The other advantages of Test Odyssey as a test automation tool are as below:


You no longer need to write endless scripts for test cases.Test Odyssey has a user friendly interface where you enter simple keywords in English, the tool in turn networks with the framework and does the rest.

as the tool is cloud based, any number of your testers or developers can login from any device/ any location to access the tool!

Again as it is a cloud based test automation tool your team does not need to suffer from ANY tool down times.

You no longer need to shell our huge payments for user licenses, you can scale your usage, up or down as per your business volumes.

You no longer need to suffer from disconnects between the manual and automation testing teams. You can import the manual test cases into the tool itself for further review by the whole team.

When you keep delivering frequent, incremental changes to your customer and in turn receive their feedback, you can afford to take small, calculated risks with your product and shape it to the market’s needs faster than your other competitors in the same space.

You can ship out small feature sets a couple of times a week and respond to customer requests and complaints. You can hold larger or more complicated features until they are completely ready and then “reveal” them. Either way there are no threats of final delivery timelines looming over your head all the time which is the case with non- CD practitioners.

CD gives you the flexibility to experiment. If you change the text on a button, would more users be tempted to use them? Will making the purchase flow easier, help the leads- to- conversion ration? You can get test results within minutes; there’s no longer any need to guess work involved in improving products.

With CD people are freed up from solving problems while the computers do the rest. Your testers and developers can instead develop new technologies, brainstorm product ideas and of course work through backlogs and fixes.

You no longer need to suffer from disconnects between the manual and automation testing teams. You can import the manual test cases into the tool itself for further review by the whole team.


To implement CD successfully, you would need to push tests into the repository. at the same time as the implementation code is sent. This will ensure that each code gets thoroughly tested and only the ones that pass get delivered to production.

So what are the highlights of TDD?

TDD relies on the repetition of a very short development cycle. First your developer can write an automated test case that defines either a desired improvement or a new function altogether. He then can produce the minimum amount if code needed to pass the test through the test automation tool

Once the code passes, he refractors the code to acceptable standards.


EkaTechserv Pvt. Ltd
Copyright © 2017, EkaTechserv.
All Rights Reserved.