Publicité
Check these out next
Reliable tests with selenium web driver
26 Jul 2011•0 j'aime•3,347 vues
2 j'aime
Soyez le premier à aimer ceci
afficher plus
vues
Nombre de vues
0
Sur Slideshare
0
À partir des intégrations
0
Nombre d'intégrations
0
Télécharger pour lire hors ligne
Signaler
Technologie
Formation
PawelPabichSuivre
Publicité
Publicité
Publicité
Recommandé
Selenium Users AnonymousDave Haeffner
Agile testing for mere mortalsDave Haeffner
Intro to TDDJason Nocks
Tests are Nothing, Testing is EverythingIan Pestelos #MovetheAverageUp
TestWorksConf: Experience exploratory testingMaaret Pyhäjärvi
Four Stages of Automated Testing by Bradley TempleQA or the Highway
Reliable tests with selenium web driver
- Reliable end to end tests with Selenium WebDriver Pawel Pabich, Senior Consultant at Readify blog: www.pabich.eu/blog twitter: @pawelpabich email: [email_address]
Notes de l'éditeur
- Selenium – Thoughtworks , WebDriver Google – Selenium/WebDriver a hopefully good combination of both
- 1. Well writtend, high level e2e test can play the role of live documentation.
- 1. Every time your CI build finishes succesfully a new piece of code can be deployed to production. So let’s say you don’t how e2e tests in place. Get the latests, the app is broken, figure out if it was you, not you, then who, what needs to be done to fix it. Now let’s imagine that all 20 guys on your team got the latest at the same time. 2. Accross the board
- It takes more time to investiage a broken e2e test than a unit test so every false alarm is costly.
- Happy path is easy, use unit tests for testing edge cases There is this attitue that tests are not deployed to Production so they don’t need the same attention as prouduction code. Wrong. Does not matter C#, Test or JS Test Recorders – not need to use them and then clean up the mess they create. I would rather start with clean code. It’s faster.
- it’s a faster, if it takes 5 seconds to load the homepage and every tests needs to load it so each tests is 5 second longer than it needs to be External system, you don’t controll them so they are down your tests fail, you can have integration tests but keep them separate We all know that but with e2e it is even more important
- Show the app first and explain DB Start with simple test (simple) Add ajax, show how to use (simpleajax) – works and doesn’t, every now and then Add 2s delay ,Debugging, TakeScreenshot (debugging) Fix the code with Thread.Sleep (fixedajax) – what’s wrong with this code, increase to 30s, waste of time Fix properly (reliableajax) (and decrease controller Thread.Sleep) show how it affects test execution time Change controller T.Sleep to 7 s and show TimeoutException, False/TE, bad API Fix with (betterretry) and show with 7s Optional: visibility (anotehr test) Long page load (hardcoded to 60 sec) but sometimes need (eg. Ncover), extensions method We’ve see some problems with finding elelements using CSS selectors If API not good enough, use access to IJavaScriptExecutor
Publicité