Software Testing
- Software testing is a methodology to find bugs in the software. OR
- Software testing is a process of Verification and validation. OR
- Testing is a process of gathering information by making observations and comparing them to expectations.
There are few terms which can confuse even the experienced testers. I have searched these terms on the net and getting different results on every website. I think we should discuss these terms so that we can have actual idea about these testing terms:
Testing Types
1. White box testing (Also known as Clear Box Testing, Glass Box Testing, Open Box Testing and Structural Testing): Used to test internal based application.
2. Black box testing (Also known as Skin Box Testing, Closed Box Testing and Behavioral Testing): Used to test functional based or requirement based application.
3. Gray box testing: Used to test web applications. It is a combination of both White box & Black box testing.
Testing Techniques (Testing approach)
The most popular Black box testing techniques are:
1. Equivalence Partitioning
2. Boundary Value Analysis
3. Cause-Effect Graphing
4. Error-Guessing
The White-Box testing techniques are:
1. Statement coverage
2. Decision coverage
3. Condition coverage
4. Decision-condition coverage
5. Multiple condition coverage
6. Basis Path Testing
7. Loop testing
8. Data flow testing
Software Testing Check List
Sometimes testers confused when they have assigned any testing task for any product. They dont know from where they should start the testing. To keep this in mind, I have collected information from many websites. Also I have put my inputs and updated the information in simple form. I have created a Checklist for website testing as well as Checklist for Desktop application Testing.
Checklist covers the following steps:
Step 1 - User Interface Testing (GUI Testing)
Step 2 - Functionality Testing
Step 3 - Interface Testing
Step 4 - Compatibility Testing
Step 5 - Security Testing
Step 6 - Performance testing
- Software testing is a methodology to find bugs in the software. OR
- Software testing is a process of Verification and validation. OR
- Testing is a process of gathering information by making observations and comparing them to expectations.
There are few terms which can confuse even the experienced testers. I have searched these terms on the net and getting different results on every website. I think we should discuss these terms so that we can have actual idea about these testing terms:
Testing Types
1. White box testing (Also known as Clear Box Testing, Glass Box Testing, Open Box Testing and Structural Testing): Used to test internal based application.
2. Black box testing (Also known as Skin Box Testing, Closed Box Testing and Behavioral Testing): Used to test functional based or requirement based application.
3. Gray box testing: Used to test web applications. It is a combination of both White box & Black box testing.
Testing Techniques (Testing approach)
The most popular Black box testing techniques are:
1. Equivalence Partitioning
2. Boundary Value Analysis
3. Cause-Effect Graphing
4. Error-Guessing
The White-Box testing techniques are:
1. Statement coverage
2. Decision coverage
3. Condition coverage
4. Decision-condition coverage
5. Multiple condition coverage
6. Basis Path Testing
7. Loop testing
8. Data flow testing
Software Testing Check List
Sometimes testers confused when they have assigned any testing task for any product. They dont know from where they should start the testing. To keep this in mind, I have collected information from many websites. Also I have put my inputs and updated the information in simple form. I have created a Checklist for website testing as well as Checklist for Desktop application Testing.
Checklist covers the following steps:
Step 1 - User Interface Testing (GUI Testing)
Step 2 - Functionality Testing
Step 3 - Interface Testing
Step 4 - Compatibility Testing
Step 5 - Security Testing
Step 6 - Performance testing
Testing Encyclopedia
1. QA, QC and Testing - Quality control is a refinement of testing, involving the formal and systematic use of testing and a precise definition of what quality means for the purposes of the test.
2. Testing Techniques - Boundary value analysis is a software testing related technique to determine test cases covering known areas of frequent problems at the boundaries of software component input ranges.
3. Negative Testing - Testing aimed at showing software does not work. Also known as "test to fail".
4. Software Testing Quotes - The only person who likes change is a wet baby.
5. Black and White Box Testing - Black Box testing refers to the technique of testing a system with no knowledge of the internals of the system.
6. Error, Bug, Defect and Mistake in Software testing - Error/bug/defect/mistake: are human interaction which produce an incorrect result.
7. Performance, Load and Stress Testing - The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression testing.
8. Testing Models - Scrum is an agile method for project management. Scrum is a method for managing work and achieving very high productivity. A popular agile method for project management, Scrum is noted for its simplicity, its high level of transparency, and a team based approach to work.
9. Severity and Priority - Severity determines the defect's effect on the application.
10. Test Cases - A set of test data and test programs (test scripts) and their expected results. A test case validates one or more system requirements and generates a pass or fail.
11. GUI Testing - GUI software testing is the process of testing a product that uses a graphical user interface, to ensure it meets its written specifications.
12. Testing Tools - Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.
13. Software Testing Miscellaneous - How can developer tell you that project has bug or not. A person who create anything can not find any bad thing in it.
14. Agile Process and QA Process - Agile means being able to quickly change direction.
15. Usability Testing - If you ask ten usability experts how to run a valid usability test, you’ll get about twenty different answers. The truth is, it really doesn’t matter too much, as long as you get users to use your application, record all issues they encounter.
16. Realities of QA
Responsibilities of Tester
a. Understand project requirements.
b. Develops and implements Test Plans that will address the testing needs of functional, regression, integration and system testing.
c. Update Test Case document.
d. Conduct Testing including Smoke, Sanity, and Execute the Test cases.
e. Update the Test Result document.
f. Attend the Regular client calls.
g. Log / File the defects in Defect tracking tool / Bug Report.
h. Verify defects.
i. Discuss doubts/queries with Development Team / Client.
j. Implements software quality assurance standards and processes.
k. Participates in design reviews/walkthroughs for projects.
l. Other duties that are within education and experience or the incumbent may be assigned for the betterment of the company.
