These are the made up stories of a team working in an Agile environment. Their daily struggles and successes are presented in a comic/parody/satirical way. Click on the image to see it in full size.
The team members are:
- Little, the main character. The team’s tester.
- Coffee, the team’s Java developer.
- Mr. Fancy, the team’s UI developer.
- Senor, the Senior Developer of the team.
- Kitty, the Scrum Master.
- Glasses, the Business Analyst.
- And the manager.
This is a work of fiction. Names, characters, businesses, places, events, situations presented are either the products of the author’s imagination or used in a fictitious manner. Any resemblance to actual persons or events is purely coincidental.
The sole purpose of this comic strip is to be humorous.
The drawings are made by hand on paper, by means of pencils and fine liners, except for the outline, by the author. Hence their imperfection.
An attribute of an HTML tag (or WebElement as you might know it from Selenium) stores valuable information about the state of that element. If we are thinking of checkboxes, a “checked” attribute will signal whether the checkbox is selected or not. For a link, the “href” attribute will tell us what location on the web it points to.
There will be times when your Selenium tests will need for an attribute of a WebElement to have an expected value. This signals that the state you expect your product to be in is correct. Before any other steps will be performed, you will need to make sure that the value of the attribute is correct, and for this process asserts are quite frequent. Enter “thewaiter” library, which has methods for you to wait for the attributes, not only to equal a text, but to also contain it, or to equal/contain it ignoring whitespaces or the case. Continue reading thewaiter: wait for WebElement attribute. To equal, contain a String, with variations.
Naming is one of those underrated things when it comes to test automation code. Many times, when you look at variable or even test method names, they are not very suggestive and you have a hard time figuring out what their purpose is. In this post you will find a few reasons why it is important to name things properly, and some tips about how to find the good names your code deserves. Continue reading Better Test Code Principles: Use proper naming, for everything
Once you have your automated regression suite in place, you can create a scheduler to run them periodically, without any manual intervention. Mostly you will use Jenkins jobs (or some similar CI tool) to trigger them and have them running on an environment of your choice. Just because they are called “regression tests” it does not mean they are only meant to be run once before a release. They are in place to help validate your system, so you can run them as often as you want. Continue reading The Automated Regression Suite. Part 2 of 3. When to run the tests.