Selenium and Continuous Intergration
0 likes305 views
This document discusses full scale automation using Selenium. It covers the history of continuous integration, the key principles of a CI manifest including committing code frequently and fixing broken builds immediately. Continuous integration systems use Selenium to automate main actions like triggering tests, updating code, analyzing results, and deploying changes. Adopting these practices helps reduce risks, remove repetitive manual processes, and establish greater confidence in the software from automated testing.
1 of 20
More Related Content
What's hot (19)
Ad
Viewers also liked (10)
Ad
Similar to Selenium and Continuous Intergration (20)
Selenium and Continuous Intergration
- 1. Full Scale Automation Using SeleniumAUTOMATED-TESTING.INFO1
- 3. Automation3
- 4. History4
- 6. Integration Process Iteration -> Nightly -> Continuously6
- 7. Continuous Integration . . . 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… Martin Fawler7
- 8. Book8
- 9. CI ManifestCommit Code FrequentlyDon’t Commit Broken CodeFix Broken Builds ImmediatelyWrite Automated Developer TestsAll Tests and Inspections Must PassRun Private BuildsAvoid Getting Broken Code9
- 13. Selenium RC13
- 14. Selenium GRID14
- 15. How it looks like15
- 18. ConclusionReduce risksReduce repetitive manual processesGenerate deployable software at any time and at any placeEnable better project visibilityEstablish greater confidence in the software product from the development teamLet’s review what these principles mean and what value they offer.18
- 19. Quality means doing it right when no one is looking.HENRY FORD19