Functional & Performance Test Automation with CI
2 likes2,717 views
The document discusses the importance of Continuous Integration (CI) in software development, emphasizing its role in making defect detection easier. It highlights the team's use of various CI tools and the modular CI pipeline approach, while also discussing how testers can leverage CI environments for early defect detection. Additionally, it provides insights into the use of Rake, a Ruby build tool, for task management and reporting.
Functional & Performance Test Automation with CI
- 1. Flex Your Testing Automation Muscles with Development CI Leonard Fingerman ([email protected]), Agile Tester
- 2. Words of Wisdom“Continuous Integration doesn't get rid of bugs, but it does make them dramatically easier to find and remove” (Martin Fowler)
- 3. Our Team8 developers3 product owners2 testers1 designer
- 4. Our Product (not a sales pitch)
- 5. Our CI ToolsCruiseControl-> Team City -> Hudson -> JenkinsModular CI pipeline approach is keyWell-supported source control system (e.g. Git)CI de-coupled build tool(s) (e.g. Ruby/Rake)
- 7. CI, the Automated Testing Platform…Typically CI is in the developer domain
- 8. Testers can and should exploit CI environment for earlier defect detection CI, the Automated Testing Platform…Scheduling tasks is built-inRun-time environments can be setup and torn down via build tasks (e.g. Ruby Rakefiles)Reporting & trending is available via plug-insNotification is built-inVisible to the entire team
- 9. CI - Testing PipelineCI – Dev pipeline .exe
- 10. Build SetupJenkins makes it easy
- 11. What’s Rake ?A simple Ruby build tool similar to makeRakefiles (rake‘s version of Makefiles) defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax to worry aboutCan specify tasks with dependenciesA well-defined library of tasks to make creating rakefiles easier
- 12. Rake Examples
- 15. Artifacts
- 16. Performance Test Trending (Jenkins plugin)
- 17. Questions ?JoEllen Carter ([email protected])Leonard Fingerman (leonard.fingerman @versionone.com
Editor's Notes
- #4: View from live dev-cam – remote members dial in for standup and this is what they see.Here’s the rest of the room – we are powered by the arc – Friday afternoon furniture re-arranging resulted in some powerful fengshui – seems to help the flow of communicationStart video at 1:45http://dl.dropbox.com/u/22563350/CIMG0491.mp4
- #6: JoEllenSwitching CI is not a big deal thanks to modular approach
- #7: JoEllenBuild pipeline consists of multiple, coupled builds…first build is triggered by checkinEach build after the first one is triggered by the successful completion of the previous build.Failing build means the end of the pipe for that check in..and we get to hear our wonderful build-break audio
- #8: LeonardElaborate on types of tests outside of CIMention previous experience as QA - Leonard’s personal experience from the past – did it the hard way Java w. DB Silo’d
- #9: JoEllenVisible w/o going somewhere else;Visible to remote team membersUniform/generic presentation of results & readily accessible to everyone (no permissions etc)
- #10: LeonardRake runs the install in the test environmentRake shells out to mstest to execute the testJenkins saves artifacts and produces reportJenkins
- #11: JoEllen
- #12: Leonard
- #13: JoEllen
- #14: LeonardTake another with all green
- #15: LeonardAdd more screenshots – screenshot test; formatted report with pass/fail info, trend plugin for p/f over time
- #16: JoellenAdd more screenshots – screenshot test; formatted report with pass/fail info, trend plugin for p/f over time
- #17: LeonardUsing Jenkins Performance Trending Plug-inRuby gem to xForm the XML display data for trending & charting