After spending more than a decade in the testing industry, we feel software testing can be improved.
By Technological excellence – Testing software from the inside out
By Testing acumen – Creative and practical testing thought processes
By Business value – Tangible results to the bottom line
We learn, research and teach these values and look forward to collaborate with you on them.
Latest from the Blog Book
Debugging is something generally people don’t like. Particularly problems spanning over days and sucking out all brain power. In a previous article I discussed how to avoid problems from emerging in your UI automation [...]
How much time would you guess an average programmer spends on debugging code? The few studies I’ve looked at estimate around 50% of the time. This is a great insight to improve one’s efficiency. [...]
In the previous article a brief history, main features and a very basic control flow was discussed. Moving on I’d like to go over some important points while installing Jenkins and running it the [...]
Most testers must have heard about Jenkins, and an increasing number of people are using or looking to use it in their automation and continuous integration efforts. The popularity of Jenkins is unquestionable and [...]
Latest From Daily Posts
Since testing cannot be automated, therefore no need to learn automation.
While the first half is true, the conclusion is not..
While collaborating, investigating and reasoning with people cannot be automated,
The kind of applications we are building now cannot be completely ‘checked’ in […]
When non-tech people hear ‘automated’, what does that mean for them?
From past 100 years history, Automated = losing jobs. In testing however, that’s not completely true. Here’s why:
In other industries remedial and repetitive jobs are being automated rapidly, blue collar jobs.
Lots of systems reusing different JSON schemas, which we need to mock,
By using JSON schema / template files to construct and push custom JSON messages to different systems..
Here’s where I have reached so for in solving it and the implementation steps:
To couple your framework tighty or loosely, that’s the question!
And here is my thought:
The first answer straight away is – loosely coupled off course,
Which is true, but how loosely?
The answer would be highly dependent on the context and usage, so there […]
One of the toughest jobs in an organization is change management
Because we humans don’t like going out of our comfort zone, but it’s equally important..
Those who don’t change will die out, no matter how big they are,
But how to change? I’m […]
For multiple products (with different teams) creating one huge solution,
How would you structure the automation framework? Here are few options:
Solution 1 – Separate frameworks for all products
Solution 2 – One framework for all products across the same automation type
Solution 3 – […]