Put an end to regression with codeception testing
1 like932 views
Joe Ferguson discusses the importance of regression testing using Codeception in PHP development, emphasizing test coverage metrics and the testing trinity: unit, functional, and acceptance tests. He outlines strategies to create tests from bug reports and build confidence in software quality by catching issues early. Ferguson encourages developers to incorporate thorough testing practices to improve application reliability and user satisfaction.
Put an end to regression with codeception testing
- 1. Put an end to regression with Codeception Testing Joe Ferguson
- 2. Who Am I? Joe Ferguson PHP Developer Engineer @ Aol. Twitter: @JoePFerguson Organizer of @MemphisPHP OSMI Board Member @NomadPHP Lightning Talks Passionate about Community
- 4. Assumptions You know you need to write tests You have written a test or two before You might have even like writing tests
- 5. “There are no solutions, only trade offs” - Joe Ferguson - Paul M. Jones - Thomas Sowell
- 6. How is your test coverage?
- 7. Code Metrics Code Climate - Grades your code quality Coveralls - Shows what code is not covered by your test suite PHPUnit Code Coverage Analysis
- 8. When your app crashes how hard does it crash?
- 9. “Can’t see the forest for the trees”
- 10. “Can’t see the forest for the trees”X X App on Fire unit tests ^ ^
- 11. 2 unit tests 0 integration tests https://twitter.com/thepracticaldev/status/687672086152753152
- 12. 2 unit tests 0 integration tests
- 13. 2 unit tests 0 integration tests https://twitter.com/ThePracticalDev/status/852508104914874369
- 14. Unit Tests ARE Important
- 15. Testing Trinity Unit Tests - This method works Functional Tests - This feature works Acceptance Tests - This product works
- 16. Testing Trinity Unit Tests - I know what broke Functional Tests - Something Broke Acceptance Tests - This product broke
- 18. Regression Testing is Easy**
- 19. Bug Report Scenario User reports that feature “Return Foo” always returns “Bar” Create a test to ensure that feature “Return Foo” returns “Foo” See test fails to confirm report or verify there is no bug Correct your application logic and make your user happy
- 20. You should not run into this bug again* * If you do, you know because you have a test!
- 25. Unit Test Suite
- 27. New Unit Test ./vendor/bin/codecept g:phpunit unit "AppHttpControllersHomeController"
- 29. Write our test for foo()
- 30. Run our test
- 31. Run only unit tests
- 32. Later that week…
- 33. We caught the bug!
- 35. I can do that with PHPUnit!
- 36. Functional Testing This feature works
- 38. Baked in Functional Testing
- 40. New Functional Test ./vendor/bin/codecept g:cept functional HomeController
- 41. Functional Test
- 43. Test to verify we get redirected
- 44. Run our Functional Tests
- 45. Expand Our Test
- 46. Run our Functional Tests
- 47. Test Failure
- 49. What if something breaks?
- 50. Of course our test fails…
- 51. Browser Output on Failure
- 52. Acceptance Tests This product works
- 53. PhantomJS
- 55. New Acceptance Test ./vendor/bin/codecept g:cept acceptance RegisterCept
- 56. RegisterCept.php
- 57. Run Our Test
- 58. Run ALL the tests
- 59. There is not much difference between functional and acceptance tests
- 60. Reuse Test Logic
- 63. Run our tests
- 64. There is a problem with our configuration of Codeception
- 65. Create a Clean DB Snapshot
- 66. codeception.yml
- 68. Codecept Build
- 69. DB is cleaned up after
- 70. Testing for Specific Content
- 73. Recap Unit tests are important! Use functional and acceptance suites to test operation of you applications Turn every bug report into a regression test so you’ll catch issues faster Too many regression tests? Could indicate workflow or UI/UX issue in your application
- 74. Questions?
- 75. Feedback! https://joind.in/talk/b7324 Joe Ferguson Twitter: @JoePFerguson Email: [email protected] Freenode: joepferguson Contact Info: