Downloaded 64 times
Uploaded byAnand Bagmar
To Deploy or Not-To-Deploy - decide using TTA's Trend & Failure Analysis
The document discusses the importance of test automation and continuous integration (CI) for successful software development. It introduces the Test Trend Analyzer (TTA) as a tool for trend and failure analysis of test runs. Additionally, it emphasizes the need for teams to effectively structure their test automation strategy and provides information on how to implement TTA in CI environments.
More Related Content
Similar to To Deploy or Not-To-Deploy - decide using TTA's Trend & Failure Analysis
To Deploy or Not-To-Deploy - decide using TTA's Trend & Failure Analysis
- 1. TO DEPLOY, ORNOT TO DEPLOY? DECIDE USING TEST TREND ANALYZER (TTA) Anand Bagmar Test Practice Lead
- 2.
- 3. WHAT DO YOUEXPECT FROM THIS SESSION?
- 4.
- 5. Test Automation A PRACTICETHAT MAKES TEAMS SUCCESSFUL?
- 6. Test Automation A PRACTICETHAT MAKES TEAMS UNSUCCESSFUL?
- 7.
- 8.
- 9. TEST AUTOMATION PYRAMID Unit Manual/ Exploratory Integration JavaScript View Web Service UI Cost Impact Time Business- facing Tests Technology- facing Tests
- 10.
- 11. ICE-CREAM CONE ANTIPATTERN Manual / Exploratory UI Web Service View JavaScript Integration Unit
- 12. Web Service View JavaScript Integration Unit Developers TestPyramid QA Team Test Pyramid DUAL TEST PYRAMID ANTI-PATTERN Manual / Exploratory UI Web Service
- 13.
- 14. How does yourTest Automation Pyramid look like?
- 15. OK… so that’s Automation… What’s Next?
- 16. CONTINUOUS INTEGRATION (CI) ”…is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible…." - Martin Fowler, ThoughtWorks Chief Scientist Ø http://www.thoughtworks.com/continuous-integration
- 17. CONTINUOUS INTEGRATION (CI)PROCESS
- 18.
- 19.
- 20. HOW ARE YOURTEAMS STRUCTURED ?
- 21. Product 1 Product3 Product 2 Product 4
- 23. IS YOUR PRODUCTIS READY TO GO TO THE NEXT LEVEL ? HOW DO YOU KNOW ?
- 24. DOES ALL TESTSPASSING MEAN NO DEFECTS?
- 25.
- 26. TTA DEMO Trend Analysis FailureAnalysis Admin Upload Data Dashboards
- 27.
- 29.
- 30. TTA - TRENDANALYSIS Pyramid View Comparative Analysis Test Execution Trends
- 34. TTA - FAILUREANALYSIS Compare Runs Failure Analysis External Dashboards
- 35.
- 39. How does itwork?
- 40. COLLECT TEST RUNDATA IN TTA Manual Upload Automatic Upload
- 41.
- 42. Job(s) Triggered Run Tests RunTests Run Tests CI INTEGRATION
- 43. Test Execution Machine CIJob Triggered Clean Compile Setup Run Tests Return to CI Test Execution Command
- 44. For TTA towork …
- 45. Test Execution Machine TestExecution Command CI Job Triggered Clean Compile Setup Run Tests Return to CI Send Test Results to TTA
- 46. The Power thisbrings to the Teams
- 47. Test Execution Machine TestExecution Command Send Test Results to TTA Ant / Maven / Gradle / Make / Rake … xUnit / testNG Java / C# / Perl / Python / Ruby … GO / Hudson / Jenkins / Bamboo / .. CI Job Triggered Clean Compile Setup Run Tests Return to CI
- 48. How to useTTA? https://github.com/anandbagmar/tta
- 50. How can youhelp?
- 51.
- 52. Use and GiveFeedback
- 53.