Powerful Test Automation Practices: A New Series

Welcome to our series of article enclose you to tried-and-true practices and patterns that help teams make worthful automated tests. Your squad can apply these basic concepts to make up tests that quickly inform you about the outcomes of the latest changes to your software production, with a reasonable investment of time. In this first instalment, we explore the value of effective use of assertions in exam.

Part 1: The Importance of Being Assertive

This is not an effort to rectifyOscar Wilde. Nor will it proclaim the virtues of being less faint. Rather we ’ re proceed to talk about the use of assertions in examination.

A Steep Hill to Climb

If you ’ re coming to test mechanisation from manual examination, you have a outrageous and potentially painful hill to climb. You need tolearn one or more programming languages, such as Python, Ruby, Java, JavaScript, Swift, or C #. You need to con theirassociate testing fabric, such as RSpec, PyTest, JUnit, Mocha, or others. If your team is using a domain-specific lyric (DSL) such as Gherkin to specify tests, and/or testers and coders collaborate to automate, you may not need to learn how to pen codification. In any case, it pays to get conversant withyour product ’ s architecture, as well as the technologies associated with the applications you ’ re testing. Perhaps you ’ ll need to plunge more into the details ofHTML, CSS, JavaScript,and various coating frameworks -- and that ’ s just for web applications! And then there arecontinuous integration (CI) and delivery (CD) systemslike Jenkins, TeamCity, Spinnaker, Concourse, Codeship, TravisCI, CircleCI, and more. And the need-to-learn list continue with version control, such as git, build tools like maven, gradle, webpack, bundler, and so on.

In all of this, it ’ s easy to forget that you ’ re still just trying to teach a machine how to accomplish repetitive tryout and cheque. It ’ s easygoing to overlook the things computers don ’ t know how to do but that you do easily and naturally, sometimes without even realizing it. By that we mean all the things you consider when shape that software behaves aright. You look at spelling, conjunction, visibleness, info content, graphical layout, and more. We have lists of things we ’ re supposed to check, but there are likewise the things that we don ’ t need to be told. Beyond that, the charming thinking machine that are our brains notice when things “ simply don ’ t seem right. ”

But computers don ’ t have your checklist, they just do what they ’ re told to do, and they sure don ’ t have a sense of what ’ s right or not. As a test automator, you need to transform all these scene of your perception into codification. This is where assertions come into play.

The Greatest Test Case

Picture for a mo the better examination example you always saw. Of course, it included all of the steps and data you postulate to exercise the application. But if it quit there, it wouldn ’ t have be a outstanding tryout case. Sure, getting through it would narrate you that nothing had gone horribly wrong, but it certainly wouldn ’ t give you a high confidence that it did everything correctly.

The outstanding test case also includes tilt of the behavior and presentationyou should await during and after each step. These expectations might hold tramp from mere reminders to detailed descriptions. Either way, they gave you a checklist of the most important thing to verify for each stride. Where relevant, they belike included the method you could use to verify them. Modular exam cases also include the expected state of the application before and after the test example as a unit so that you can put them in the right context when combined with other trial cases.

Breaking Down Your Perceptions

In test mechanization, you verify each of these elements that a outstanding test lawsuit checks with assertions.The first big challenge is simply to be witting of the things you may not have been explicitly conscious of when you were evaluating if it “ just look right. ” This is not a technical challenge, which is why it ’ s easy to overlook when faced with the more obvious technical challenge of automation.

Even with an amazing test case, you affix what ’ s written with your own observation. Here are a few categories and examples of things that can be assertions:

Each of these can be interrupt down into little constituent or described in more point. Color may be delineate with a gens or an RGB value. Size could be in pel, ems, rems, inch, mm, point, and more. Alignment can be represented by equivalence of coordinate dimensions. And so forth.

Conquer the Hill

Assertions are feedback.Take a look at any automated UI examination you ’ re currently using. If you have a UI test that navigates to a new page but doesn ’ t verify that it has landed on the correct page, that could lead to job as the test proceeds. Use assertions to make sure your UI page meet your squad ’ s visual and design quality standards. Use them to check fault handling - does the UI return the correct message? Does it put the exploiter in the correct place? Is everything happening in an acceptable time frame? Make sure the state of various components in your application change as expected via assertions.

Asserting to confirm that the application is up to snuff in all those different calibre attributes can give you confidence that each new change to the production gives some value to the customer. These checks will pave your way through that dreadful trial automation learning curve.

In part 2, we dive deeper into how to formulate assertions for optimal feedback. We tempt you to post any questions you have in the comments here!

Meet the authors: