It occurred to me lately, after chatting with some people from the testing community, that not everyone runs automated tests or does any kind of testing in the production environment. For me that seems a bit unnatural, since i have been doing it on all the projects that i worked on. So, here are a few thoughts that might convince you that you do need to run automated tests even in production: Continue reading Why you need to test your production environment
Checkout my article for TechBeacon on Top 5 Apache Commons utilies for automation engineers: https://techbeacon.com/5-best-apache-commons-utilities-automation-engineers
Checkout the talk i had with Joe on why automation is fun and why you should also get into automation: https://joecolantonio.com/testtalks/183-test-automation-fun-corina-pip/
My last conference of the year recently wrapped up in beautiful Budapest. I took part, as a speaker, in 2 days filled with practical and useful advice, in a fantastic location. Continue reading My HUSTEF 2017 conference experience
You are writing some automated tests with Selenium, that require you to fill in some text fields in a form. You are pretty confident you typed the values you expected to type, into the field you expected to type into. But, here are just 3 reasons why you should write some code that checks that you actually wrote what you thought, where you thought, before submitting the form you are trying to fill in.
‘Twas a not so warm day in October, that in Vilnius awesome testers united to talk about their crafts. Some crushed candies, some with machines worked, others Selenium magic performed. And this is how it all unfolded. Continue reading My TestCon Vilnius 2017 experience
When automated test are running, they are either running on your own machine (when you write them or run them to check something), or in your CI.
When you run the test on your machine, if there are failures, it might be easy for you to look at what is running (if you have some visual tests, that interact with either browsers or apps on your machine). You can just rerun a failed test and visually inspect for failure reasons. But, if tests are running on a CI machine, visual inspection is either very difficult or even impossible. You might not have access to connect to that machine, or to see how tests are being run. Continue reading Test design: write tests with proper console output to easily identify failure reasons