Manual Testing Tutorial
Manual testing is one of the earliest type of software testing. Here the tester manually tests the software for defects (performs a set of functional tasks). The tester follows a set of test cases derived from a set of requirements. Here a test plan is followed. It requires the tester to step into the shoes of the enduser and test the application as if he was to use it. There are several stages of Manual testing.
Manual Testing Tutorial Full
They are Unit Testing Integration Testing System Testing User Acceptance Testing Please find various links related to the different aspects of manual testing on the left hand side. As “recently as 1998, in one Fortune 100 company, performance testing was conducted while one test engineer sat with a stopwatch, timing the functionality that another test engineer was executing manual testing”. Elfriede99 Manual testing is that part of software testing that requires operator input, analysis, or evaluation.
Manual Testing should be documented in great procedural detail. This helps in repeating the tests consistently, in the way they were intended. Manual Test case generation The Manual test cases are developed in the implementation phase of the project. Functional specification document, Test Plan and design document are taken as input for the manual test case generation. The manual test case specifies actual input values and expected results. The goal in the generation of manual test cases is to exercise the component’s logic and to setup testing scenarios that will expose errors, omissions and unexpected results.
The task is carried out by testers and test lead and verified by Test Manager. SQA using the exploratory testing method, manually tests and then plans more exhaustive testing and automation. Manual Test case creation is expensive. Estimates run from 3-10 times the time to create and manually execute a test case. Tests which are suitable for manual testing are not necessarily suitable for test automation.
Software Testing. Aimed at breaking the system. Understand dynamic behaviour of the work product. Process of finding deviations of Observed Behaviour from Expected Behaviour. Software Testing Tips:. Never ignore any test cases. Be worried if all test cases go smoothly(pass) without noticing any defects – on the first time.
Look for additional test cases for scenarios or coverage based on the test execution. Include exceptional conditions, alternate path and boundary conditions for testing. Perform monkey testing to see work product’s behavior in all extreme conditions.
Get smart: Write effective test cases, that can give maximum coverage with minimum testing. Get disciplined: Script your test data so that testing can be done by anybody. Get thinking: Identify components that are important to be tested. Prioritize: Identify business scenarios that are important to be tested Prioritized testing ensures that the important areas are covered first. Communicate: Status reporting to interested groups on product quality status can be precise. Challenges in Software Testing. Attitude.
Avoid - 'Writing test cases is too hard and boring.' . Avoid - 'My code is too simple for tests.'
. Coverage. Scenarios of functions. End User needs. Time & Cost. Schedule.
Workload. Budget. Inadequate planning. Testing Plan. Test Data. Test Environment Still, Good Software Testing improves confidence!
Software development goes through a chain of process. It starts with requirement analysis phase and ends with the maintenance phase.
There are two important phases of software development, namely coding and testing. Testing phase is an important phase, as it verifies and validates that the software has been developed according to the requirements of the user. Software testing can be carried out using two methods which are automation testing and manual testing. The names of software testing types are indeed self-explanatory. This manual testing tutorial will help you to understand the basics of software testing in general and manual testing in particular.
The entire process of manual testing goes through four phases. First phase is known as unit testing.
It is the job of the developer to test units of the code written by the developer himself. In some cases, the code may also be tested by a peer. Integration testing is second phase of software testing.
It is carried out, when big chunks of codes are integrated to form a bigger block. Either black box or white box testing is carried out in this phase. The next phase is system testing phase. The software is tested for all possibilities to rule out any kind of abnormality in the system. Normally black box testing technique is used in system testing phase. User acceptance testing is per se the last stage of manual testing.
In this phase, software is tested keeping the end-user in mind. There are two types of acceptance testing which are used, namely alpha testing and beta testing. There are three types of software testing, under which all software testing activities are carried out. They are:. White Box Testing: Testing of internal structure of the software is known as white box testing. Black Box Testing: This testing strategy is used to test different functionality of the software, that is being developed. Gray Box Testing: The software is tested to find defects of any kind, whether in code or in structure.
There are other types of software testing, which are used to test a product to ensure that the software meets requirements of the end-user. They include:. Functional Testing. Smoke Testing. Usability Testing. Validation Testing.
Compatibility Testing. Sanity Testing. Exploratory Testing. Security Testing. Regression Testing.
Recovery Testing. Performance Testing (This includes 2 sub-types - Load Testing and Stress Testing). Software testing methodologies are divided into static testing techniques and dynamic testing techniques. Software review and static analysis by using tools are methods, which come under static testing techniques. Specification based testing techniques, structure based testing techniques and experience based testing techniques are all included under dynamic testing technique.
Equivalence partitioning is one of the important strategy used in specification based testing technique. Take a look at the article titled for detailed information.