To reply to the issue posed in the title, we have to determine what software testing is. In fact, it's made up of two components:
verification: are we building / doing what's right?
validation: am i building / carrying it out right?
Verification we can be reassured that we have understood what we should wish to achieve, and validation makes sure that that which you get matches that, as well as being well-implemented. This is simply not just applicable to software development, either, even as shall see.
Do You Need To Do Software Testing?
In case you are owning a project that requires computers, then you will need to do some software testing. At the simplest point of interaction, this may you need to be ensuring that a bit of software does what you want (requirements testing) prior to deciding to roll it out through the company.
For all those actively commissioning software being created (whether it's a simple implementation of the Wordpress blog or even an App), software testing becomes an important milestone inside the plan. Software developers should not be entrusted to perform all aspects of software testing, but at the same time oahu is the responsibility of the commissioning the program to make sure that the requirements are accurate.
You can't blame a developer for delivering something which does not satisfy, when the requirements are unclear or incomplete. This is actually the first stage of testing.
When (in the Project) Should Software Testing Be done?
Software testing needs to be performed at the earliest opportunity. Encouraging agile techniques that result in early delivery of (even incomplete) software packages enables testing to start early enough that course corrections can be carried out at a relatively small cost.
The later that these same corrections are essential, the greater they will cost. The more costly time for you to fix an item is when it's finished - sadly, many folks believe in leaving software testing towards the end from the project, which plays a part in the failure statistics in software development projects.
When (in the Development) Should Software Testing Be Performed?
Again, the solution to this can be easy to say - as early as possible.
As a developer (programmer/scripter) it's responsibility to provide fault-free software. Now, it's not always possible as a result of time and/or financial constraints, but it needs to be the aim.
To achieve it, testing each bit of code separately needs to be conducted; and also to do that, you must know what the outcome (expected result) of executing the code under various conditions needs to be. This, consequently, uses thoroughly and properly tested design.
So, testing must begin as early as possible - on the design phase - and continue through to integration testing.
The suggestions above is true for other projects, too:
requirements testing: is truly the internet site, report, outcome, app / application you want?
component testing: do all the various parts which have been selected / created do what we expect?
integration testing: do every one of the components come together properly?
stress / performance testing: can it be scalable?
These four aspects of software testing are as applicable to developing an application, web service, or standalone shrink-wrapped product since they are to something as seemingly disparate as developing a house, creating a Formula 1 car or owning a shop.
testing, then, isn't only for software, but software testing is becoming a lot more vital in modern projects as for entertainment and work to consider over many facets of working life.
