Download as PDF, PPTX
![Tests Reporting
—
1. Standard runners
2. Report tabs
3. Custom format:
1. Transformation + Report
consumer (XML Report
Processing)
2. Service messages
echo "##teamcity[testStarted name=‘test.MyTest']"
echo "##teamcity[testStdOut name='test.MyTest' out='My Test output']"
echo "##teamcity[testFinished name='test.MyTest' duration='150']"
echo "##teamcity[testStarted name='test.MyFailedTest']"
echo "##teamcity[testFailed name='test.MyFailedTest' message=‘test failure'
details='MyFailedTest has failed']"
echo "##teamcity[testFinished name='test.MyFailedTest' duration='150']"](https://image.slidesharecdn.com/runningtestsinci-avito-170901140613/75/Continuous-Integration-JetBrains-25-2048.jpg)
More Related Content
Similar to Запускаем тесты в Continuous Integration - Сергей Пак (JetBrains)
![[Perforce] Adventures in Build](https://cdn.slidesharecdn.com/ss_thumbnails/perforce-adventures-in-build-slides-130523180506-phpapp02-thumbnail.jpg?width=640&height=640&fit=bounds)
![Computer Networks 01[1 using all terms].pptx](https://cdn.slidesharecdn.com/ss_thumbnails/computernetworks011-251214040533-327dd9f8-thumbnail.jpg?width=640&height=640&fit=bounds)
Запускаем тесты в Continuous Integration - Сергей Пак (JetBrains)
- 1. Running tests in ContinuousIntegration — Sergey Pak Jetbrains
- 2.
- 3. Test Automation — 1) Saveresources
- 4. Test Automation — 1) Saveresources 2) Faster feedback
- 5. Test Automation — 1) Saveresources 2) Faster feedback 3) Continuous testing
- 6. Continuous Testing — 1) Nomanual test execution
- 7. Continuous Testing — 1) Nomanual test execution 2) Tests in VCS
- 8. Continuous Testing — 1) Nomanual test execution 2) Tests in VCS 3) Automated tests are a part of the application code
- 9.
- 10.
- 11.
- 12.
- 13. Prepare environment — 1. BuildAgent 2. Prefer containers (Docker) or VM template
- 14. Prepare environment — 1. BuildAgent 2. Prefer containers (Docker) or VM template 3. Configure environment before build
- 15. Prepare environment — 1. BuildAgent 2. Prefer containers (Docker) or VM template 3. Configure environment before build 4. Privileges for BuildAgent 1. Prefer roles for VM
- 16. Clean-up environment — 1. Writein build directory
- 17. Clean-up environment — 1. Writein build directory 2. Cleanup created files, rollback modifications 1. Prefer VCS functionality 2. Swabra
- 18. Clean-up environment — 1. Writein build directory 2. Cleanup created files, rollback modifications 1. Prefer VCS functionality 2. Swabra 3. Kill created processes (Swabra)
- 19. Clean-up environment — 1. Writein build directory 2. Cleanup created files, rollback modifications 1. Prefer VCS functionality 2. Swabra 3. Kill created processes (Swabra) 4. Investigation takes time
- 20. Tests Execution — • Frameworks(Selenium) -> Utility (Maven, MS Build) • Tools (Testcomplete) -> Plugin/script 1. Both can be run in CI
- 21. Tests Execution — • Frameworks(Selenium) -> Utility (Maven, MS Build) • Tools (Testcomplete) -> Plugin/script 1. Both can be run in CI 2. Store tests in XML
- 22.
- 23. Tests Reporting — 1. Standardrunners 2. Report tabs
- 24. Tests Reporting — 1. Standardrunners 2. Report tabs
- 25. Tests Reporting — 1. Standardrunners 2. Report tabs 3. Custom format: 1. Transformation + Report consumer (XML Report Processing) 2. Service messages echo "##teamcity[testStarted name=‘test.MyTest']" echo "##teamcity[testStdOut name='test.MyTest' out='My Test output']" echo "##teamcity[testFinished name='test.MyTest' duration='150']" echo "##teamcity[testStarted name='test.MyFailedTest']" echo "##teamcity[testFailed name='test.MyFailedTest' message=‘test failure' details='MyFailedTest has failed']" echo "##teamcity[testFinished name='test.MyFailedTest' duration='150']"
- 26. Run tests. Reusecode — 1. Parameterization 2. Templates 3. Agent requirements 1. No gold agents* * Except performance tests
- 27. Run tests. Reusecode — 1. Parameterization 2. Templates 3. Agent requirements 1. No gold agents* Demo * Except performance tests
- 28. Performance tests — 1. Goldagent + Gold build
- 29. Performance tests — 1. Goldagent + Gold build 2. Failure condition by time 1. Specify exact test names/wildcard
- 30. Performance tests — 1. Goldagent + Gold build 2. Failure condition by time 1. Specify exact test names 3. Statistics (per build/test/etc.) over the time
- 31. Performance tests — 1. Goldagent + Gold build 2. Failure condition by time 1. Specify exact test names 3. Statistics (per build/test/etc.) over the time Demo
- 32. Build dependencies — 1. Snapshotdependencies 2. Build Chain
- 33. Build dependencies — 1. Snapshotdependencies 2. Build Chain 3. Build promotion 1. Permissions 2. Tags
- 34. Build dependencies — 1. Snapshotdependencies 2. Build Chain 3. Build promotion 1. Permissions 2. Tags 4. Artifact dependencies
- 35. Build dependencies — 1. Snapshotdependencies 2. Build Chain 3. Build promotion 1. Permissions 2. Tags 4. Artifact dependencies 5. Schedule trigger (+ watched builds + tags)
- 36. Build dependencies — 1. Snapshotdependencies 2. Build Chain 3. Build promotion 1. Permissions 2. Tags 4. Artifact dependencies 5. Schedule trigger (+ watched builds + tags) 6. Shared resources
- 37. Test Results — 1. Compositebuild (2017.2)
- 38. Test Results — 1. Compositebuild (2017.2) 2. Report tabs
- 39. Test Results — 1. Compositebuild (2017.2) 2. Report tabs 3. Test history
- 40. Test Results — 1. Compositebuild (2017.2) 2. Report tabs 3. Test history 4. Flacky tests
- 41. Test Results — 1. Compositebuild (2017.2) 2. Report tabs 3. Test history 4. Flacky tests 5. Investigations
- 42. jetbrains.com Thank you for yourattention —