1 / 16

Experience Report: Test Automation in an Agile Environment

Experience Report: Test Automation in an Agile Environment. Len Vaz Oct 13, 2010. Software Development Process. 1 week sprints No UATs Use Jira for Bug Tracking Use Grass Hopper for user stories Test cases tied to user stories

dora-nunez
Télécharger la présentation

Experience Report: Test Automation in an Agile Environment

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. Experience Report: Test Automation in an Agile Environment Len Vaz Oct 13, 2010

  2. Software Development Process • 1 week sprints • No UATs • Use Jira for Bug Tracking • Use Grass Hopper for user stories • Test cases tied to user stories • Corresponding blank test cases entered into the automation framework • Automated builds using Hudson

  3. Review the product • Documentation • Engineering • Product organization

  4. Breaking down system to test Malware analyzer

  5. Test Environment • Architecture • Hardware • Software • Tools

  6. Architecture

  7. Database schema

  8. Resources • Hardware • Software • People (Planning) • Standards

  9. Automation • IDE • Eclipse Downloads • Pydev - Python IDE for Eclipse • Frameworks • PyUnit - Python Unit Testing Framework • Setting up common code • Standards

  10. Reporting • Using Visualizations • Interactive Charts • Google Visualization API Reference

  11. Report

  12. Report Header

  13. Report Details

  14. Report Details

  15. Report Performance

  16. Lessons learned • Continuous improvement • Continuous integration testing • No TDD – lot more work for QA • Lack of Infrastructure integrated testing • Estimation is not an easy process • Without reporting – no extra resources

More Related