Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Continous testing for grails
Similaire à Continous testing for grails (20)
Dernier
Dernier (20)
Continous testing for grails
- 1. Continuous Testing for Grails Jeff Winkler
- 2. TDD FTW http://vinkamat.com/2011/tdd-unit-testing-and-benefits/
- 3. TDD http://vinkamat.com/2011/tdd-unit-testing-and-benefits/
- 4. TDD Focus: Unit Tests • Types – Junit TestCase – Grails: UnitTestCase – Groovy: TestCase – Spock: Unit Spec
- 6. Experimental Results on 22 Sophomores, 6.170
- 7. • A controlled experiment has shown that continuous testing has a statistically significant effect on developer success in completing a programming task, without affecting time worked. Developers using continuous testing were three times more likely to complete the task before the deadline than those without. • Most participants found continuous testing to be useful and believed that it helped them write better code faster, and 90% would recommend the tool to others
- 8. Tool Comparisons • Grails 1.37 vs Grails 2.01 • CT: Auto-test, InfiniTest
- 9. 1.37: Rinse, Lather, Repeat
- 11. Continuous Testing Options • InfiniTest – http://infinitest.github.com/ – For IDEA or Eclipse – groups.google.com/group/infinitest-users • Auto-test – http://grails.org/plugin/auto-test • JUnitMax from Kent Beck – $100 – Health? Not tried
- 12. Auto-test The plugin will monitor the project directory and will attempt to run only the subset of tests affected by what changed. This is very rudimentary - for example, if you modify BookController or BookControllerTests or BookControllerSpec, it will run test- app BookController
- 13. Autotest 1.01
- 14. Infinitest
- 15. Tip: Ignoring Integration Tests
- 16. Criteria: Spock
- 17. Test Execution in coding environment, interactive results.
- 18. Scores Spock Tests in Results in Auto-run Interactive Score same env same env 5 points Results Test-app 1 IDE (Eclipse) 4 Auto-test 1.0.1 6.5 InfiniTest 8
- 19. TLDR • InfiniTest for IDE users – same environment • Auto-test for non-IDE • Neither is perfect.
- 20. Results • MIT Study: Devs 3X more likely to finish task on deadline; 90% would recommend continuous testing. • Try It!
Notes de l'éditeur
- TDD alternates between Green, Red.
- Really Running the Tests, alternating Red/GreenNot batching
- Unit tests are FastGood tooling supportWork without spinningup Grails.
- Continuous Testing Idea Started @MIT, 2004in backgroundreduce time & effort to runReduce Change size if a problem is foundSame as Continuous Compilation for dev, or CI for an organisation.Work by watching .class files on disk. Save->Compile->Tests Run
- Concept: Ignorance time: How long something broken, that you did not know about.Fix Time is correlated with Ignorance time. Same as continuous integration!
- Issues: Run tests in different environment than coding environment. Alt-Tab to run tests, get results.
- GoodColor Less Verbose Same JVMPeek @ResultsBad:- Still separate environment
- InfiniTest was briefly commercialAuto-test is Grails only, no IDE integrations.JUnitMax – status?
- Good:Fairly dumb heuristicsBad: Separate environment.
- Demo-------Prefs/EnableRebuild project – tests run when classes change.Change AnotherClass.*Smart* about what to run… sometimes misses things.Open source – feel free to add fixes!Shows errs for all open projects.Won't run if compilation errs in any open projects.