Teste Explratório - TDC 2011

Click to edit Master title style Exploratory Tests: Click to edit Is this text styles Master really effective? Second level Author: Third level Neli Duarte Fourth level Fifth level‹date/time› ‹footer› ‹#›

Click to edit Master title style Agenda Overview Click to edit Master text styles Exploratory tests definitionS What really are exploratory testing? Second level X Ad Hoc? Exploratory Apply the method: exploratory techniques Third level & Negative points Positive Case study Fourth level Conclusion Fifth level‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#› 2

Overview Click to edit Master title style Not strictly defined Suitable concept about exploratory testing Click tofeeling Master text styles Manager’s edit Don’t have formal documentation Second level application is a exploratory technique “Poking around” on Third level Exploratory tests is just different way to executing tests but it doesn’t means that it is a messy!!! Fourth level Fifth level It is a pretty effective method to test software. “Exploratory” is very embracing word and it is also applied on technical side; See next… ‹date/time› TDC-SP/ Jul 2011 ‹footer› ‹#›you can use “exploratory” way on performing tests like ad hoc or other one, you arereally “exploring” the software and you are able to call it as exploratory testing, butyou can’t say that exploratory testing are ad hoc tests because they are completelydifferent.Not different than others aspect, exploratory testing is one more thing that is notstrictly defined yet. That’s why I am writing it, to explain the suitable concept aboutexploratory testing and help you to understand; although this can also beenimproved and changed further. =) 3

Click to Exploratory tests definitionS edit Master title style “What’s the big deal? Exploratory testing is random pounding on the keys. Nothing to it. My toddler does it every day.”[1] Click to editTesting,” said one of the developers, “that’s where the … “Oh, Exploratory Master text styles tester does a bunch of wacky, random stuff, right?” … [2] Second level Exploratory, or ad hoc testing, can be an especially useful testing strategy… [3] level Third Fourth level "Exploratory testing is an interactive process of concurrent product exploration, testFifth level test execution.” James Bach, Satisfice (2001) design and **Different literature defines exploratory tests in a different concepts ‹date/time› TDC-SP/ Jul 2011 ‹footer› ‹#›It is just to show up that different literature defines exploratory tests in a differentconcepts, people think different and defined their own perspective regarding topic. Iam not trying to dictate the right concept, I am just telling you the most suitableconcept to define exploratory test allowing for “exploratory” is pretty embracingword. 4

Click toreally areMaster title style What edit exploratory testing? It is another test execution method!!! Click to edit Master text styles Second level Third level What is NOT exploratory tests? Fourth level Test type (system…) Test phase (design, execution…) Fifth level Pocking around Test Approach (white…) Test Strategy *‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›Test strategy: ET can be part of the strategyTest Phase: Planning, analyses, design, execution, report and so on.Test Type: It is the tests applied according to the development phase.(component, system, integration, sanity, UAT and so on)Test Approach: White, Black or Grey box testing.Test Strategy: Besides it is a part of the test strategy, ET by himself isnot a complete test strategy.“Pocking around”: Definitely poking around is not any testingtechnique. 5

Exploratory X Ad Hoc?Click to edit Master title style No, they aren’t against Click to edit Master text styles Second level Third level Fourth level Fifth level ** Both Independent of formal documentation to be executed Are related to the tester’s creativity‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#› So, Ad hoc testing can differ from Exploratory by the lack of previous planning, but it does not mean that it is a worthless technique of testing. If fact, we can think as ad hoc as a part of the exploratory testing, once that you are creating your test as long you are running it. We dare to establish that: all ad hoc testing are exploratory testing, but not all exploratory testing are ad hoc.

Apply the method: exploratory techniquesClick to edit Ad Hoc title style Master No planning neither structure Bugs are found on by accidentally and it is hard to reproduce Click to edit Master text styles Is kind of exploratory testing but Exploratory Testing is not Ad Hoc Second level to apply Ad Hoc tests? So, is there any scenario Yes, there are!! Third level Software’s stability Get knowledge about new software: Fourth level Hands on by Test Lead / Test Manager Tests blocked level Fifth Developers before delivery code Apply it, depends on the defined strategy. Testing software is a creative area and these examples are just to give you ideas to define the best strategy Bug’s traceability: well reported‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›Ad Hoc tests are executed without any plan or structure. Tester justopen the application and going through, browsing according to hiscreative. Bugs are found on by accidentally and it is hard toreproduce due to don’t follow any structure.Software’s stability: After code freeze in the development phase or aspart of regression tests, Ad Hoc might be a good practice to help ontest software’s stability due to force and browsing in the softwarewithout plan or pre-requirement.Get knowledge about new software: When new resource is joined tothe team and if some bug is found, it is additional on learning process.Hands on by test lead: Test leaders/Test Manager tend to don’t testsoftware in details as Testers does, in this case Test Lead canperforming Ad Hoc test to get feeling about the software that he isresponsible. 7

Apply the method: exploratory techniquesClick to editChecklist title style Master Checklist is created contained highlights regarding software to be tested Click to edit Master text styles Checkpoint Examples of scenarios to be explored Second level Send SMS concatenated, not concatenated, in roaming, not roaming and so on Third level Receive SMS connected to phone, not connected, during a calling or not and so on Fourth level Delete SMS delete saved SMS, not saved, in Fifth level inbox, sent box and so on Save as draft when receive a call, when leave the screen and so on Note: Clean environment when move to next checkpoint due to bug’s reproduce Strong skill on application Bug’s traceability: well reported‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›In this case before starting tests a checklist is created containedhighlights regarding software to be tested. It means main function ofthe features not in details or any steps.Let’s imagine that it is software to use SMS function from your mobiledevice. There are options to send, receive, delete, save as draft andso on, then you create a checklist using these main function of thesoftware, just like that: 8

Apply the method: exploratory techniquesClick to edit Master title style Session based testing was created to track the testing they were performing. (James and Click to edit Master text styles Jonathan Bach) Second level Sessions are time-boxes within Third level which the testing occurs. Each session has a charter (a little Fourth level mission) and results in a session report. Fifth level Bug’s traceability: well reported‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›Session based testing was created by James and his brotherJonathan Bach as a need to track the testing they were performing.Since Exploratory testing is a king of a ad hoc processing, notrestricted to pre-defined test steps or test procedures with mission offinding bugs without previous noticed and find them fast sessions-based testing were created. 9

Click to edit &Master title style Positive Negative points + Has a planning and structure of testing Click not depends Master text styles be created to edit of any formal documentation to Easy to reproduce defects found Do Second leveldocumentation or often changing Projects with lack Easy to maintain and change Third level Minimize the time - Fourth level Fifth level Might to depend on the test experience Easily misused Not advised to be used as unique method to assure test coverage (happy path may not be coverage) KT: Knowledge transfer‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›

Case study –Click to edit Master title style Ad Hoc - Experienced tester & Error guessing Click to edit Master text styles Project scenario: Validate promotions from telecom operator. (E.g. Mammy’s day), requirements were created from marketing area. Second level Solution: Getting input from Product Manager (from marketing area) Third level Testers used past experience and creativity Error guessing based in both points above Fourth level Fifth level Key point: Testers experienced, even they hadn’t experience to the application the testers had a lot experience in software testing.‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›

Click to edit Case/Study –tests style Master title Checklist Sanity Click to edit Master text styles Project scenario: Weekly meeting and test team had to report sanity test Second level result. (4 companies), new build at same day. Third level Solution: Checklist and Test points Fourth level Test type: sanity Fifth level Test objective: identify high priority bugs on new build Key point: Experienced testers in software testing and strong skill on application.‹date/time›V EBTS Apr 2011 ‹footer› ‹#›

Case Study –Click to editBased Testing title style Session Master & Charter Project scenario: Agile (Scrum), 1 tester, 12 developers Click to edit Master text styles Solution: Second level (not detailed steps) Chart to save time Focus on learning about product Third level Vulnerability areas Working together to developers Fourth level Bugs were found, value was added and the client was satisfied with Fifth level the software quality. Key point: Experienced tester in software testing and agile methodologies. **assumed risk on using only this method‹date/time›V EBTS Apr 2011 ‹footer› ‹#›

Click to edit Conclusion title style Master Click to bugs: avoid vicious scripted test styles Get escaped edit Master text Second level Fits in several project scenarios: agile, not agile, test type Third level Used according to the test strategy: save time… Fourth level Improve test’s effectivelevel used as additional method on test phase Fifth when Smarter Testing!!!‹date/time›V EBTS Apr 2011 ‹footer› ‹#›

Click to edit Master title style Click to edit Master text styles Second level Questions Third level Fourth level Fifth level‹date/time›TDC-SP/ Jul 2011 ‹footer› ‹#›

Click to edit Master title style Click to edit Master text styles Second level Third level Fourth level Fifth level nduarte@br.ibm.com neli.duarte@gmail.com‹date/time› ‹footer› ‹#›

Click to edit Master title style Click to edit Master text styles Second level Third level Backup Fourth level Fifth level‹date/time›V EBTS Apr 2011 ‹footer› ‹#›

ReferencesClick to edit Master title style [1]. http://www.quardev.com/articles/slides_breaking_down_and_building_up_explorat Click to edit Master text styles ory_testing_skill [2]. http://testobsessed.com/2006/04/19/rigorousexploratory- Second level testing/RigorousExploratoryTesting [3]. http://blog.platinumsolutions.com/node/353 Third level [4] Oxford Advanced Learners Dictionary of Current English, A S Hornby, OXFORD – Oxford University Press 2000 Fourth level Images from: Fifth level http://www.competence.co.in/ http://bonniesbooks.blogspot.com/2011_05_01_archive.html http://www.ibm.com/us/en/‹date/time›V EBTS Apr 2011 ‹footer› ‹#›

Teste Explratório - TDC 2011

by Elias Nogueira on Jul 09, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Teste Explratório - TDC 2011 — Document Transcript