When Should Testing Be Automated?

Dec. 11, 2012 - PRLog -- We can hear the conversation about whether and when testing should be automated during long period of time. It is important to keep in mind that testing actually covers a number of different techniques and this question cannot be answered just yes or not.
So you need to look at every type of software testing which needs to be performed and decide on a case-by-case basis.
But in what way can you decide?
First of all, you need to think over what you are asking. You are trying to decide if a test you need to do should be done with the help of script\code and made into an automatable, repeatable test or if you want to manually conduct the test every time you change something. After that you need to think about the kind of testing you want to do. You should also make a decision about the price of automating the process as opposed to the price of repeating the test. You need to think over the price of carrying out the automated test compared to our manual test.
Ultimately, you need to cogitate about the price of the situation when something going wrong and a defect occur in production. After this you can make a decision if you think the price of automating is worth the price and effort compared to manual testing. Let’s consider some initial problem domains and the common thought process when faced with the question of whether to automate or not.
If we speak about unit testing, our main attention will be on the business logic and process. Probably, this is the most consequential segment of any. If this logic is wrong, it can cause a lot of troubles because it commonly will only appear in production. Everybody knows that defects found in production are the most costly to fix. Having the production that the unit tests in place provide against software bugs http://qatestlab.com/services/sample-deliverables/bug-rep... making their way into production is definitively an essential factor.
According to the business logic, if you have created your system in a testable kind then you should find that the tests are easy to write and carry on. If you want to change something to the underlying logic due to the design of the system being testable, then the price of maintaining the costs should be small, especially when combined with the lower cost of ownership of the core system.
Nevertheless, your automated tests http://qatestlab.com/services/our-qa-services/automated-t... will verify the business logic is proper; you could also manually test this.
On the other hand, there are some chief blockers to this conviction. To test the business logic you would need to go via a UI, either the major applications or the custom wrote UI.
There are 2 probable troubles occur here:
1.   The chief application might have defects, which blocks you from testing the logic.
2.   It hasn’t been written yet.
Add to this the case that after every code change you would need to manually re-enter all these values and edge cases into the UI and verify the result was as you expected based on either a specification or previous experience. As far as we’re concerned, this makes automating the business logic essential.



QATestLab is independent, offshore software testing company located in Kiev, Ukraine. QATestLab performs testing of products on each stage of software development cycle.