Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous automation


Published on

All about Continuous Automation Process

Published in: Business
  • I thought that execution of the tests is a part of the Continuous Integration system. At least in our team we are doing this during more then 15 years.
    Are you sure you want to  Yes  No
    Your message goes here

Continuous automation

  1. 1. TheContinuous Integration Automation<br /><br />@ImGredy<br />
  2. 2. Buzz<br /><ul><li> So, What??? Do you mean Continuous Automation?
  3. 3. Nope, it is similar but different
  4. 4. But why?
  5. 5. Cauze test automation is not development only, it is a part of testing by the way
  6. 6. And?
  7. 7. And then we just need to adopt the “Continuous” to automated testing. Let me show why…</li></li></ul><li>Motivation<br />Motivation<br />Functional testing code should be isolated from software code<br />Test and software independency is a must to avoid any influence, e.g. test code relying on software code can cause false positive or negatives in results<br />Changes in test code and test suites should be resulted in reporting at once - triggered run<br />Every commit to head/trunk evolves update of local test artifacts repository<br />Testing code quality addresses by frequent execution iterations<br />Non stop execution with fresh “stable” cutoff of testing code provides clean and actual testing results. Broken tests are revealed as early as possible. Confidence<br />Test automation Change Management and Version Control should be conducted in the same way as code development<br />Branching, diff, merge, patch, commits, revisions, baselines, tags, etc. – are essentials for any kind of code. Test code is not exclusion <br />
  8. 8. Motivation<br />Static code analysis, peer code review, traceability, refactoring, code metrics…<br />All these perfectly works for automated testing and even benefit to entire process<br />
  9. 9. Reporting<br />Finally – the key artifact of automated testing is REPORTING<br />
  10. 10. Prod (Stable) Tests<br />SCM<br />Triggers update<br />+<br />Commits<br />Static code analysis<br />Prod (Stable) Framework<br />Deploy on QA env<br />Test Reporting DB<br />Test cloud<br />fills<br />Test artifacts<br />Continuous test execution<br />affords<br />Defects<br />Benchmark analysis<br />Test Reporting<br />Metrics<br />Traceability<br />Test code <br />changes<br />promotes<br />
  11. 11. Advantages<br /><ul><li>Reducing time on test stabilization
  12. 12. Reducing manual effort by process automation
  13. 13. Functional testing becomes reliabilitytesting by the way
  14. 14. Early feedback on products quality
  15. 15. Results of contribution is available for everyone early
  16. 16. Often delivery – more confidence
  17. 17. Tests are remaining workable
  18. 18. Broken tests get noticed at once (e.g. unmet GUI or API changes)
  19. 19. Clear and wise reporting
  20. 20. Compliance with best S/W engineering practices
  21. 21. Predictable and managed process (metrics, trends, benchmarking, real time reporting of any level)
  22. 22. No risks of dependencies with dev process and CI</li></li></ul><li>Benefits<br /><ul><li>Keep Green line
  23. 23. Transparent Collaboration
  24. 24. ROI is going up as long as you practice Continuous Automation
  25. 25. Process and technical championing in test automation
  26. 26. Repeatable process by machines, not by people
  27. 27. Resources are not idling
  28. 28. Long-run usually finds hidden and tricky bugs such as memory leaking, security flaws, failover and something that could be analyzed from application logs
  29. 29. Scalability is by default (adding new stands and tests as 1-2-3)
  30. 30. Again – confidenceand steadiness</li></li></ul><li>Feel free to call it<br />Continuous Automation (CA) <br />
  31. 31. Test<br />Dev<br />Continuous integration<br />Continuous automation<br />Quality<br />Product<br />
  32. 32. is a Continuous Automation (CA) tool<br /><br />@ImGredy<br />