Guide to End to End Test Driven WordPress Projects
•
1 recomendación•255 vistas
Do you get notified if some crucial functionality on your website was changed or broken? Is automated testing part of your daily routine or deployment process? If not, then you are risking of losing parts of your website or even entire project. Testing is no longer developers realm and everybody should get involved and get the benefits of test driven development. In this session we will cover: - basics of end-to-end testing - test reports and who should receive them - automated testing best practices - how clients can benefit from automated testing This session is aimed for - everyone who is interested in getting daily reports on how healthy their project is - teams who would like to improve communication internally and externally by means of test reports - project managers and developers interested in collecting data about their project over time
Recomendados
Recomendados
Más contenido relacionado
Similar a Guide to End to End Test Driven WordPress Projects
Similar a Guide to End to End Test Driven WordPress Projects (20)
Más de Vladimir Roudakov
Más de Vladimir Roudakov (20)
Último
Último (20)
Guide to End to End Test Driven WordPress Projects
- 1. Testing any day: guide to end to end test driven Wordpress projects WordCamp Brisbane 22 Jul 2017 Vladimir ROUDAKOV
- 3. This session about ● end-to-end testing ● reports & outcomes ● practices ● benefits #WCBNE @VladimirAus
- 4. This session is for ● project managers ● clients ● developers ● testers #WCBNE @VladimirAus
- 5. This session describes ● common language ● aims to complete project ● communication #WCBNE @VladimirAus
- 6. This session does not contain ● technical information ● specific technology ● specific methodology #WCBNE @VladimirAus
- 7. This session about me ● developer ● tester ● team leader ● educator #WCBNE @VladimirAus
- 8. How much should we spend on testing?
- 9. Why testing? ● service ● money ● reputation #WCBNE @VladimirAus
- 10. Junior developer
- 11. ● interest in output only ● no interest in quality ● gets intern job ● finds bug in software #WCBNE @VladimirAus
- 12. ● not impressed ● process disruption ● no processes ● treated as extra work #WCBNE @VladimirAus
- 13. 3 times Compare plan to spend on testing actually spends on testing
- 17. Reasons for project failure ● poorly defined goals ● optimistic expectations ● project is too complex #WCBNE @VladimirAus
- 22. Gathering Requirements ● Login form ● User area #WCBNE @VladimirAus
- 26. Common Language
- 30. Client doesn’t buy code! Client buys solution!
- 33. - Login - User area #WCBNE @VladimirAus
- 34. R1: Login R2: User area - Login - User area #WCBNE @VladimirAus
- 35. - Login - User area R1: Login R2: User area - Login - User area #WCBNE @VladimirAus
- 36. Testing... - Login - User area R1: Login R2: User area Ready? - Login - User area #WCBNE @VladimirAus
- 37. Testing... - Login - User area Yes, but not tested R1: Login R2: User area Ready? - Login - User area #WCBNE @VladimirAus
- 38. Testing... - Login - User area Yes, but not tested R1: Login R2: User area Ready? Feature is ready - Login - User area #WCBNE @VladimirAus
- 39. Testing… Found a problem with login form - Login - User area Yes, but not tested R1: Login R2: User area Ready? Feature is ready - Login - User area Testing… - cannot login - inconsistency with button colour #WCBNE @VladimirAus
- 40. What to test? ● Fields ● Functionality ● Error message ● Colours ● Everything #WCBNE @VladimirAus
- 41. ● Login form ● User area #WCBNE @VladimirAus
- 42. As anonymous user I want to login #WCBNE @VladimirAus
- 43. As anonymous user I want to login from login page located at '/wp-admin' #WCBNE @VladimirAus
- 44. ● As anonymous user I want to login from login page located at '/wp-admin' ● As anonymous user I want to login from home page #WCBNE @VladimirAus
- 45. As anonymous user I want to login from home page and want to be redirected to login page with the following error message when login is incorrect #WCBNE @VladimirAus
- 46. As anonymous user I want to see links to "Restore password" and "Registration" pages #WCBNE @VladimirAus
- 47. Documents
- 48. Documents ● Changelog ● Test Reports #WCBNE @VladimirAus
- 51. Testing Tools
- 52. External Tools ● Selenium ● Nightwatch ● Behat ● WP End to End Tests #WCBNE @VladimirAus
- 53. Services ● BrowserStack ● SauseLabs #WCBNE @VladimirAus
- 54. In conclusion ● Communicate ● Produce tests as team ● Test ● Report #WCBNE @VladimirAus
- 55. Questions?
- 57. Resources: videos Making testing fun | Andy Zaidman | TEDxDelft https://www.youtube.com/watch?v=IfXVEz_mMHI Nightwatch.js Tutorial - Selenium Automation Testing with javascript https://www.youtube.com/watch?v=wfwgt-7IZLQ
- 58. Resources: tools and services Selenium - Web Browser Automation http://www.seleniumhq.org/ SauceLabs http://www.saucelabs.com/ BrowserStack https://www.browserstack.com/
- 59. Resources: libraries NightwatchJS - nodeJS wrapper for Selenium http://nightwatchjs.org/ Behat - php library for automated testing http://behat.org/ WordPress.com End to End Tests - repository https://github.com/Automattic/wp-e2e-tests