Let's Start- Basics of Software Testing

What is Software Testing?

1.One of the Software Development Life Cycle (SDLC) Activity performed by a dedicated team to ensure the developed product has NO major failures and NO security vulnerabilities.

2.It ensures the Quality is met as per customer requirement along with organization standards.

3.It gives how much confidence we can have about the stability of the End Product

4.It ensures or strives to have zero bug products.

 

Why do we Software Testing?

1.Quality- To meet quality standards with as minimal to Bug free(Ideal scenario) product.

2.Security vulnerability-To eliminate security vulnerability.

Hackers gets unauthorized access to data. They steal user details and use it for their benefit. If your product is not secured, users won’t prefer your product. Users always look for trusted products. Testing helps in removing vulnerabilities in the product.

It is very important aspect for Banking domain projects and lot of times hacker attack such products. Product will not considered for release to customer if any security issues and I personally have observed the customer will reject and it is warning sign to company if such bugs are discovered in the release build.

 What are the different Methods of Software Testing?

 1.White Box testing- Programmer write unit level test cases and execute it .It can be single function and they try to execute the lines of code with different input.

2.Black Box testing.- This is testing carried by Software Test Engineer/QA of the project. They run manual testcases or automated script against the product released to QA. The testcases can be Behavioral based, requirement based. In the type of testing the developed code is not tested or review instead application behaviour and issues are raised to Dev team.

Main Types of Black box Testing:

1.Functional-Testing carried out based on functional requirement Specification document.

2.Non-Functional-Testing carried out based on non-functional requirement like performance, security, usability

What are the documents requirement for Black box testing?

1.Business Requirement Specification(BRS)

2.Functional Requirement Specification(FRS)

3.Test cases- Scenario, Testdata, Expected Result and Actual results

How to do Black Box testing?

1.Based on requirement and specification valid input and expected output are examined.

2.QA can use valid input(positive test scenario) and invalid (negative test scenario) to check the product behaviour on different conditions.

3.All the expected results are determined and mentioned testcases.

4.The Actual output and expected output is then considered to say if the test is passed or failed.