1 / 33

ALM Live: Team Test

ALM Live: Team Test. Explained and distilled for Everyone! Micael Herkommer m icael.herkommer@inexor.se. Introduktion. Micael Herkommer Developer Coach & Solutions Architect INEXOR | EPiServer Professional Services VSTS Inner Circle Cornerstone EBC Advisor. Team Test.

plato
Download Presentation

ALM Live: Team Test

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ALM Live: Team Test Explained and distilled for Everyone! Micael Herkommer micael.herkommer@inexor.se

  2. Introduktion Micael Herkommer Developer Coach & Solutions Architect INEXOR | EPiServer Professional Services VSTS Inner Circle Cornerstone EBC Advisor

  3. Team Test • Vad är tester egentligen? • Varför ska jag bry mig? • Hur kan jag använda tester? • Vad kan jag vinna med tester? • Hur kommer jag igång med tester?

  4. Agenda • Motivera er med behovet • Gå igenom ursprungsproblemet • Kom igång med Team Test • TFS och VSTS • Lite tips på vägen • Frågor & avslutning

  5. ALM • Application Lifecycle Management • Ett organiserat system!

  6. Det lilla ordet: men... ”Alltså det ser verkligen jättebra ut, kanon, MEN...”-ett vanligt kundcitat vid en normal leverans någonstans i ett mjukvaruprojekt nära dig

  7. ...men • Förändra den negativa reaktionen till något positivt: ”Gud-va-kul!” • Förståelse = motiv • Varför vill kunden ändra? • Organisera din reaktion & verktyg • Använd en metodik!

  8. Kommunikation • Beställare • Användare • Affärsanalytiker • Projektledare • Utvecklare • Testare • Driftsättare • Förvaltare

  9. Låt oss backa lite...

  10. Myter och sanningar

  11. You can’t test a program completely • Possible inputs too large to test • Too many possible paths • User interface issues

  12. You can’t test the program’s response to everything • You’d have to test all valid input • You’d have to test all invalid input • You’d have to test all edited input • You’d have to test all variations on input timing

  13. You can’t test every path

  14. You can’t find every design error

  15. You can’t prove the program is correct using logic

  16. Tester’s objective: • Program verification! • Not possible! • Can’t test thoroughly enough • Error discovery means tester failed • Ineffective attitude: sucess at all cost

  17. Så varför testa? • Syftet är att finna problem! • Syftet med att finna problem är att få dem fixade!

  18. Team Test och TFS

  19. Typer av tester • Enhetstester • Manuella tester • Webbtester • Webbservicetester • Grupperade tester • Generiska tester

  20. Testverktyg • Test viewer • Test manager • Test results

  21. WIT • Work items • Bug • State • Triage • Assignment • Details • Cycle of life

  22. About the Tester • The tester’s main goal is to discover and communicate problems with the product that could adversely impact its value. The tester must understand the context for the project and help others to make informed decisions based on this context. A key goal for the tester is to find and report the significant bugs in the product by testing the product. Once a bug is found, it is also the tester’s job to accurately communicate its impact and describe any workaround solutions that could lessen its impact. The tester makes bug descriptions and steps for recreating the bugs easy to understand and follow. The tester participates with the entire team in setting the quality standards for the product. The purpose of testing is to prove that known functions work correctly and to discover new product issues.

  23. 1-Define Test Approach • Determine the project context. • Determine the test mission. • Assess possible testing techniques. • Define the test metrics.

  24. 2-Write Validation Tests • Identify the test area and environment. • Identify test case flow details. • Write the test cases.

  25. 3-Select and Run a Test Case • Determine which test to execute. • Identify the test configuration. • Get the build. • Execute the test. • Analyze the test results. • Close the work item.

  26. 4-Open a Bug • Identify a bug. • Assign the bug.

  27. 5-Conduct Exploratory Testing • Establish session length. • Meet persona expectations. • Envision new persona goals.

  28. Demonstrationer • Enhetstester • Extern indata • Webbservicetest • Webbtest • Inspelning • Validering • Svarstider • Värden

  29. Demonstrationer • Manuella tester • Prestanda • Lasttester • Grupperade

  30. Team Test • Vad är tester egentligen? • Varför ska jag bry mig? • Hur kan jag använda tester? • Vad kan jag vinna med tester? • Hur kommer jag igång med tester?

  31. Rekommendationer • Testing Computer Software • Wiley • Kaner | Falk | Nguyen (1983) • Software Testing w/VSTS • Wrox

  32. Frågor och avslutning

  33. Frågor och avslutning Tack för er tid! Ha en fortsatt trevlig dag!

More Related