Results 1 to 5 of 5

Thread: Steps to start testing

  1. #1
    Moderator
    Join Date
    Oct 2005
    Answers
    305

    Steps to start testing

    After getting build, What is next step to start testing? What are the exact things? Can u explain?

    NOTE : [This question was asked by Murali.OS]


  2. #2
    Junior Member
    Join Date
    Jul 2006
    Answers
    3

    Re: Steps to start testing

    Hi,

    First we need to perform the Smoke testing on the build ...we need to test the build as per the release scope..... major functionality should be tested.

    Once the major functionality of the build is passed as per the release scope..We will put a mail to the Dev people saying that "We are Accepting the build for testing"...if the major functionality of the build is failed as per the release scope..... then we will put a mail to the DEv people saying that "WE are not accepting the build for testing as the Smoke test failed
    and here are the results 1)Result1 2)Result2"..................

    If passed then .............
    We start executing the testcases ......and log the issues in Bug tracking tool if the testcase is failed...............

    After completion of execution of testcases ...we perform Adhoc testing and then Database testing...............

    And if any updations are required in Testcases as per new functionality in the build .........we will update the testcases .................

    So this is the process...........

    If u have any doubts regarding this ...please feel free to ask me.....

    Regards,
    Vasavi


  3. #3
    Moderator
    Join Date
    Sep 2006
    Answers
    920

    Re: Steps to start testing

    Smoke--Sanity---Functional(actual testing).


  4. #4
    Expert Member
    Join Date
    Nov 2006
    Answers
    518

    Re: Steps to start testing

    Follow the steps for better results

    1) We receive the very first s/w build from dev team.
    2) We apply level 0 sanity testing to test its testability and understandability.
    3) If we find it is not, then the sanity test is failed and we report the problems as to why it is not testable or understandable.
    4) We get a fresh s/w build.
    5) We apply level 0 sanity testing to the fresh build again. And let us say it is passed this time. Once a build is passed Sanity testing, it is called a "Stable build".
    6) We now start our actual testing process by applying the written test cases (functional testing).
    7) We found some of the test cases failed. We report the bugs to the dev team.
    8) We receive modified build (after resolving the reported bugs).
    9) We start regression testing on modified build.
    10) Now go back to step 7.

    Step 7, 8 and 9 are ongoing……


  5. #5
    Junior Member
    Join Date
    Dec 2006
    Answers
    2

    Re: Steps to start testing

    hi , According 2 me after making builds , each build is smoke tested seperately.After then all the builds are integrated and then smoke tested complete module.

    If u find d actual answer , then pls. forward me 2.


    Regards
    Gaurav
    9911185394







    Quote Originally Posted by Lokesh M View Post
    After getting build, What is next step to start testing? What are the exact things? Can u explain?

    NOTE : [This question was asked by Murali.OS]



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact