What Is The Preferred Order for Performing Testing On Information Technology Projects?

I have been working in the IT services sector for 13 years now and right now working as a manager. So, I am qualified to tell you about the preferred Order for Performing Testing. There are different methodologies followed in information technology projects. For example waterfall methodology, Agile Scrum, Scaled agile, etc. I have been working in agile methodology since 2011. Most large companies use agile scrum or scaled agile in information technology projects.

While development the developers should perform unit testing. And preferably the dev team should automate the unit test cases so that they can reuse them. Every time there is a code deployment in upper environments, such as QA environment, UAT environment, Prod env, there will be a Sanity test performed to make sure the new deployment did not cause any severity 1 issue, or it did not break anything major.

Next comes integration testing, which is like say each developer is building different components, and now when multiple components are ready, integration testing will make sure all components talk to each other, work together and produce what it is supposed to produce.

Functional testing or system testing or system integration testing, are pretty much the same thing. The QA team makes sure the application is behaving the way it should.

Preferred Order for Performing Testing by users which are known as user acceptance testing or UAT comes at last before production. This is performed by the client. But, UAT is the last stage mostly for applications that are not going on the internet. Otherwise, there will be load testing/ performance testing, security testing too.

But being a novice you need to understand first a client provides requirement, the IT team that includes business analysts, system architects, developers, quality analysts testers who then analyze the requirements, and make sure that they understand the vision. Once the analysis phase is done, then they start to build, which is another way of saying, technically the architect defines how to achieve the client vision, developer code to fit the vision and then the quality assurance team perform testing to ensure the quality of the product.

This is a helicopter view. Now there are many types of testing. Such as unit testing- which is performed by the developers, who test their code before they deliver the code to QA or for system / functional testing.

Functional or system testing is done by the quality assurance testers. Preferred Order for Performing Testing is always after developers make the functional code ready. If during QA or functional testing bugs are found then, the developer will fix them. and send the fix back for a retest.

Once functional testing is successfully done, the code goes for user acceptance testing, which is usually performed by the client. And when that is done the code is usually deployed to the production. This is where the actual use of the product begins. So the preferred order for performing testing is before after build code is implemented but has not gone to production yet. The goal of so many rounds of testing is not to make the product defect-free, but to make the product better and best of quality. Gradually more bugs come out, which gets fixed and that is how the product gets better.

2 thoughts on “What Is The Preferred Order for Performing Testing On Information Technology Projects?”

  1. Good day,

    My name is Eric and unlike a lot of emails you might get, I wanted to instead provide you with a word of encouragement – Congratulations

    What for?

    Part of my job is to check out websites and the work you’ve done with thedividendhoarder.com definitely stands out.

    It’s clear you took building a website seriously and made a real investment of time and resources into making it top quality.

    There is, however, a catch… more accurately, a question…

    So when someone like me happens to find your site – maybe at the top of the search results (nice job BTW) or just through a random link, how do you know?

    More importantly, how do you make a connection with that person?

    Studies show that 7 out of 10 visitors don’t stick around – they’re there one second and then gone with the wind.

    Here’s a way to create INSTANT engagement that you may not have known about…

    Talk With Web Visitor is a software widget that’s works on your site, ready to capture any visitor’s Name, Email address and Phone Number. It lets you know INSTANTLY that they’re interested – so that you can talk to that lead while they’re literally checking out thedividendhoarder.com.

    CLICK HERE http://talkwithcustomer.com to try out a Live Demo with Talk With Web Visitor now to see exactly how it works.

    It could be a game-changer for your business – and it gets even better… once you’ve captured their phone number, with our new SMS Text With Lead feature, you can automatically start a text (SMS) conversation – immediately (and there’s literally a 100X difference between contacting someone within 5 minutes versus 30 minutes.)

    Plus then, even if you don’t close a deal right away, you can connect later on with text messages for new offers, content links, even just follow up notes to build a relationship.

    Everything I’ve just described is simple, easy, and effective.

    CLICK HERE http://talkwithcustomer.com to discover what Talk With Web Visitor can do for your business.

    You could be converting up to 100X more leads today!

    PS: Talk With Web Visitor offers a FREE 14 days trial – and it even includes International Long Distance Calling.
    You have customers waiting to talk with you right now… don’t keep them waiting.
    CLICK HERE http://talkwithcustomer.com to try Talk With Web Visitor now.

    If you’d like to unsubscribe click here http://talkwithcustomer.com/unsubscribe.aspx?d=thedividendhoarder.com

Comments are closed.