Test::Class::Moose
•
6 j'aime•5,869 vues
Test::Class::Moose combines Test::Class, Moose and Test::Most to take test suites to the next level. It gives you unparalleled levels of control and information for you test suite.
Recommandé
Contenu connexe
Similaire à Test::Class::Moose
Similaire à Test::Class::Moose (20)
Plus de Curtis Poe
Plus de Curtis Poe (19)
Dernier
Dernier (20)
Test::Class::Moose
- 3. • • • • OO tests for OO code Nice performance boost Easy to organize tests Already use Moose info@allaroundtheworld.fr
- 5. 1. Getting started with Test::Class 2. Inheriting Test::Class tests 3. Making your testing life easier 4. Using test control methods 5. Test::Class tricks On www.modernperlbooks.com info@allaroundtheworld.fr
- 24. Solution? ✘ ✘ ✓ Instantiate the object correctly? info@allaroundtheworld.fr
- 25. • • • • We've written two classes We've written two test classes We've seen test inheritance … but it broke our test! info@allaroundtheworld.fr
- 29. • It works • But we constructed our object twice • Wash/rinse/repeat for every test method? info@allaroundtheworld.fr
- 30. Method Phase Before each test class Before each test method After each test method After each test class info@allaroundtheworld.fr
- 31. • • • • • Connect to a database (often in startup) Set up fixtures/transactions (setup) Clean fixtures/rollbacks (teardown) Disconnect from database (shutdown) And more … info@allaroundtheworld.fr
- 43. • • • • • • • Only run API tests Only run unit tests Run correct code coverage Run Jenkins tests Run DB tests Create fixtures only if the test needs it Skip network tests if the network is down info@allaroundtheworld.fr
- 52. • • • • Fine-grained control xUnit-style testing Full Moose integration Reporting info@allaroundtheworld.fr
Notes de l'éditeur
- No need to add empty control methods
- No need to add empty control methods
- No need to add empty control methods
- We've skipped some usual Moose boilerplate (namespace::autoclean and make_immutable)
- Methods beginning with test_ are test methods.Two objects to every method
- This works, but we constructed our object more than once. We don't want duplicated code.