Software Testing

                         

SOFTWARE TESTING :- It is a test to ensure that the software is bug free, timely completion and according to user’s  requirement.It is also defined as verification and validation of software or product.

.

 Verification :- Verification is used when static    testing take place  where no actual code  execution is happened only documentation is  verified at the starting of the project  these    documents include requirements and  specification documents  ,the system  requirement specification and business  requirement specifications and there is no use  of code take place.

 Validation :- validation is used when dynamic    testing take place where actual code execution is     happened and this also includes matching of user requirement with the behavior of  functionality of feature that it is fulfilling the applied user  need .it is done after the verification process.

The important points to note before starting software testing :- 

1. We should know the user requirement for example-if the customer says that he want to buy a car worth  500000 rupees what car do you recommend to that customer? Than your answer should be what is your  requirement?  This is because may be the customer  needs  should be fulfilled only in 200000 rupees or may be less than that.

2. We should know the proper set up to test the required software .Environment should be intact with the  software  that is there should not be any kind of magnetic  field ,strong electric field or any kind of dust particles which can make the execution of software slow or causes  so much errors or failure in the software.

3. We should properly check what data should be entered inside the software .Failure can only take place if the wrong data is get entered by the tester so we should properly check the data  before entering the data into the input field of the software.

4. We should create test cases early in the life cycle because creating early test cases can cause less errors to be introduced in the software .it can also cause failure if we do not create test cases early in the software development life cycle because the error  which is not  caught early can be well propagate into  the different phases of software development life cycle.

5. We should properly understand the user requirement .so that we can check the functionality which totally matches the user requirements. We do not make the  wrong bugs if we have read the user specification document rightly and his will also avoid failure happened due to bad assumption by us.

FOR MORE DETAILS YOU CAN VISIT OUR WEBSITE :- http://thinknexttraining.com/