This is going to be a follow-up post in regards to the approach i showed at my SeleniumConf talk, on doing Selenium tests by using an Object Oriented approach.
I will have a series of such posts, to show more examples and to make it easier to understand how to use it. All the code presented here will be available in GitHub under this location: https://github.com/iamalittletester/learning-project. Continue reading Selenium tests, the Object Oriented way – example 1 (with code)
Here’s a new and (possibly) cool feature regarding the blog: there are now code examples to be checked out and tried that you can download from Github.
The code location is: https://github.com/iamalittletester/learning-project.
Here are some details and how to run the test project: Continue reading GitHub project available with code examples
Yey, the program for the 2017 edition of the Nordic Testing Days conference has been published, and i am glad to be among the people speaking. More specifically, i will be running a two-hour hands-on, coding workshop on Selenium tests, the Object Oriented way. It will be a very practical workshop, where one can learn how to think in an OO fashion when it comes to testing complex modules or modules that appear in several areas of the page to be tested.
Check out the full program of the conference here: http://nordictestingdays.eu/schedule and don’t forget to get your tickets! It will be great.
I am back from the SeleniumConf UK 2016 event which took place in London, and i have to say, it was a fantastic experience. I have seen some really great talks, got plenty of takeaways, and as an added bonus, as a speaker, i managed to get a sneak peak ‘backstage’.
All the talks are freely available, which is a major plus for this conference, so have a look Continue reading Lessons learned at SeleniumConf 2016
When i look at a test class, what i want to see is clean code. What i mean by that is, well a few things, but the most important one: i want the test class to hold the code for the tests, not the code for everything but the kitchen sink.
When we write tests we have a lot of data to prepare for them. Whether this is the ‘expected’ or the ‘actual’ data used in the tests, or some auxiliary code that we need, there always is some processing that needs to be done, apart from the actual asserts that a test should do. What the test class should contain is only the checking / asserting part, while having specialized classes generate all the data that is required in the test. A test class should only check the actual data against the expected data. This is the separation of concerns principle. Continue reading Write clean code for your tests by using the separation of concerns principle
So i was just recently notified that i will be among the chosen ones to speak at this year’s Selenium conference, SeleniumConf, taking place in November in London. Great opportunity this is 🙂
Checkout the program (which is still in development) here: http://2016.seleniumconf.co.uk/sessions and don’t hesitate to grab your tickets 🙂 It’s going to be awesome.
See you there.
Selenium 3 has been announced a long while ago, but it is only recently that beta versions have started rolling out. The latest beta version, 2, is now available for you to try. Continue reading Selenium 3 beta version 2 available for you to try