How to Find Defects Without a Formal Testing Process
About Us • KostCare is a Quality Assurance and Software Testing Services company. • We serve clients worldwide to ensure that they have predictability as to the quality and performance of their software. • Committed to delivering excellence in software quality assurance and testing, our strength lies in our ability to leverage the best of industry knowledge and the most advanced technology available. • KostCare is powered by Indian Acumen. Our experience over the years working with a global clientele, has allowed us to perfect our know-how in the area of IT outsourcing. • This experience has also helped us to advance our client collaboration practice, and it has given us the on going knowledge to assist our customers attain maximum returns on their outsourcing investment.
What is Ad-hoc Testing? • This is an informal type of software testing that is performed by software testers, business analyst, developers or any stake holder without referring to test cases or documentation. • A person performing ad-hoc testing usually has a good understanding of software requirements and tries to break the software and find defects with the experience and knowledge they have about the domain, requirements and functionality of the software. • Ad hoc testing is intended to find defects that were not found by existing test cases.
Characteristics of Ad-hoc Testing If you note the scenarios above, you will see something very distinct characteristics about this type of testing. They are: • They are always in line with the test objective. However they are certain drastic tests performed with intent to break the system. • The tester needs to have complete knowledge and awareness about the system being tested. The result of this testing finds bugs that attempts to highlight loopholes of the testing process. • Also looking at the above two tests, the natural reaction to it would be that – these kind of tests can be performed just once as it’s not feasible for a re-test unless there is a defect associated.
When do we do Ad-hoc Testing?
• Most of the times test teams are always burdened with too many features to test within limited timelines. • In that limited time-span there are lots of testing activities that are derived from the formal process that must also complete. • In such situations ad-hoc testing finding its way into the testing is slim. However from my experience one round of ad-hoc testing can do wonders to the product quality and raise many design questions. • Since ad-hoc testing is more of a “wild-child” testing technique that doesn’t have to be structured, the general recommendation is that it must be performed after the execution of the current test bucket is done. Another point of view is that this could be done when detailed testing cannot be performed due to less time. • In my view, I would say that ad-hoc testing can be done almost anytime – in the beginning, towards the middle and towards the end! It just finds its place at any given time. However, when ad-hoc testing must be done to bring out maximum value is best judged by an experienced tester who has in depth knowledge about the system being tested.
When not to execute? • While we’ve established how effective and fruitful ad-hoc testing can be, as a skilled and capable tester we also need to decipher when not to invest in this type of testing. • Although it is under the discretion of the tester, here are some recommendations/examples when it might not be necessary. • Avoid this testing when there is a test case for which a defect exists. In such a situation there is a need to document the test case failure point and then verify/re-test the defect when it is fixed. Hence it won’t be applicable here. • There may also be certain scenarios where customers or clients maybe invited to test the beta version of the software. In such cases this testing should not be conducted. • Another scenario is when there is a very simple UI screen that is added. Traditional positive and negative testing should suffice here to bring out maximum defects.
Types of Ad-hoc Testing 1. Bubby Testing 2. Monkey Testing 3. Pair Testing
Buddy Testing • In this form of testing there will be a test member and a development member that will be chosen to work on the same module. • Just after the developer completes the unit testing, the tester and developer sit together and work on the module. • This kind of testing enables the feature to be viewed in a broader scope for both parties. • The developer will gain a perspective of all the different of tests the tester runs and tester will gain a perspective of how the inherent design is which will help him avoid designing invalid scenarios, thereby preventing invalid defects. • It will help one think like think the other.
Monkey Testing • This testing is mainly performed at the unit testing level. • The tester parses data or tests in a completely random way to ensure that the system is able to withstand any crashes.
Pair Testing • In this testing, two testers work together on a module with the same test setup shared between them. • The idea behind this form of testing to have the two testers brainstorm ideas and methods to have more number of defects. • Both can share the work of testing and making necessary documentation of all observations made.
Ad-hoc Testing Benefits • The biggest advantage that stands out is that a tester can find more number of defects than in traditional testing because of the various innovative methods they can apply to test the software. • This form of testing can be applied anywhere in the SDLC; it’s not only restricted to the testing team. The developers can also conduct this testing, which would help them code better and also predict what problems might occur. • Can be coupled with other testing to get best results which can sometimes cut short the time needed for the regular testing. This would enable better quality test cases to be generated and better quality of the product on the whole. • Doesn’t mandate any documentation to be done which prevents extra burden on the tester. Tester can concentrate on actually understanding the underlying architecture. • In cases when there is not much time available to test, this can prove to be very valuable in terms of test coverage and quality.
Ad-hoc Testing Drawbacks • Followed from the first point, this would also result in not being able recreate defects in the subsequent attempts, if asked for information. • Another very important question this brings to light is the effort accountability. Since this is not planned/ structured, there is no way to account for the time and effort invested in this kind of testing. • Ad-hoc testing has to only be performed by a very knowledgeable and skilled tester in the team as it demands being proactive and intuition in terms foreseeing potential defect ridden areas.
Click Here For More Update Regarding Software Testing Services In Waterloo