Frontend testing with Codeception
Download as PPTX, PDF0 likes1,772 views
The document discusses frontend testing using Codeception, focusing on tools, monitoring, behavior testing, and continuous integration. It outlines key components such as a composer setup, Gherkin for defining test scenarios, and the importance of testing in production environments. Additionally, it emphasizes the role of understandable tests in building trust between project owners and developers.
Frontend testing with Codeception
- 1. Frontend Testing with Codeception Christian Keuerleber ... nope, not Unit Tests ;)
- 2. About me • Christian „Herbie“ Keuerleber • Working at punkt.de since2010 • Certified Integrator • Frontend-guy doing backend stuff • Likes to make an error only once Kabarakh – on Twitter, Slack, GitHub...
- 3. Agenda • What tools will we be using? • Monitoring • Behaviour testing • Testingin continuous integration • Questions(and hopefully answers)
- 4. Tool-Chain • Php withComposer • Chrome/Chromium andChromedriver • For CIwe might need docker
- 5. (some) Needed Composer Packages • codeception/codeception • automatically installeddependencies: • facebook/webdriver • behat/gherkin • guzzlehttp/guzzle • webmozart/assert
- 6. A completecomposer.json (formonitoring tests) { "name": "punktde/punktde-website-monitoring", "license": "GPL-3.0+", "require": { "codeception/codeception": "^3.0" }, "autoload": { "psr-4": { "PunktDePtwMonitoring": "Classes/" } } }
- 7. Gherkin? <?php classFirstCest { public function frontpageWorks(AcceptanceTester $I) { $I->amOnPage('/‘); $I->see('Home‘); } }
- 8. Gherkin! Feature:As a website user inorder to beableto seeany content I want to see the mainpage Scenario: Given I am on "/" ThenIshouldsee"Home"
- 9. Understandabletests arepartofthe foundation oftrust betweenPOs and developers!
- 10. Monitoring Is thewebsite still working? Did my changes break anything? Howwill I be notifiedif something breaks?
- 11. Monitoring • non-invasive • runsonproduction • can beactually run everywhere • runsas oftenas possible • (ideally)many small tests • usesbrowser – liketheusers
- 13. Behaviour testing • Thecodeworks as intended • Thecodesworks as definedby thePO • Edgecases andinvalidactions are considered
- 14. Behaviour testing • needs a preparedstate (fixture) • Arrange, Act, Assert • manipulates database, files andsuch • runsin its own environment • shouldrunbeforecodeis even deployed • tests can bequite largeandcomplex • usesall technologies youhave – CLI, SQL, Browser,Guzzle, ...
- 16. Let's see a live example –and howit is used ... for monitoringat least
- 17. Buzzword-Bingo! !!FREE FIELD!! user-centric Contexts Helper classes Module Actor Actor Traits Features Scenarios Scenario Outline Populator YAML data files Guzzle API Tests Artifacts Docker Tablenodes Params Database testing Reusable steps codeception.yaml punkt.de GitHub packages Environments JUnit output Background Everyone can write test files
- 19. Some good-to-knowlinks • https://codeception.com • https://cucumber.io/docs/gherkin/reference/ • https://github.com/punktde – searchfor "codeception" • https://packagist.org/packages/punktde/ • https://github.com/punktDe/codeception-demo