The assignment QA engineers

First impressions are important, second impressions are everything. So it’s time for some action. Let’s stop talking and get some serious testing done. After all, the only certainties in life are death, taxes and bugs in code!

We have formulated an assignment to assess your testing knowledge. The assignment has been devised with manual and automation testers in mind. Carefully read what to do and what not to do. The assignment consists of two parts. To check your understanding of both subjects.

Conditions

• If a completion date has not been agreed with you, please try to complete the assignment in a week;
• Please do both parts of the assignment unless otherwise stated;
• Please use Github or one of the repositories to share your code, we want to see the code next to a running test suite;
• Please make sure that we can run the automation scripts on our computers by including a readme. (that includes the setup of the automation stack itself).

What are our expectations?

Part 1: Test planning

We would like you to make an small document describing the test planning for the test activities over a 6 months time frame for an imaginary project. This project is a new eCommerce website which just started development. Until now testing has not been performed in this project. The PO/PM asked you to make a small document in which the test activities are defined for the upcoming six months until delivery. Consider it as a mini-test plan with a timeline.

Part 2: Test automation

We are expecting you to demonstrate your knowledge of test automation by sending in a fully running assignment. We expect you to have a generated report after running. Depending on your experience we also expect a framework to be set up and also a basic pipeline set up or thought about (for example maybe add a yml file). The tool you choose can be any of the tools you are aware of currently being used in the industry.

What do I need to automate, you might ask, we will leave that up to you. Make a choice of some interesting flows using the following two websites. The automation tests are made based on automation test sites available freely on the internet at the point of making these tests. You can go wild on these websites!

• http://the-internet.herokuapp.com
• http://automationpractice.com/index.php

Some challenging scenarios to automate if you need to start somewhere: 

• Access  http://the-internet.herokuapp.com/broken_images, validate if there are broken images.
• Access http://the-internet.herokuapp.com/upload and try uploading any file
• Access  http://automationpractice.com/index.php, Hover over a product from the home page and add it to the basket, then check it out as both a registered and a guest user
• Access http://automationpractice.com/index.php, Hover over one of the main categories and click on a subcategory, and filter.
• Any other interesting flow you find in the two websites 

Experienced automators

It will be nice if the framework that you build can be used on the multiple AUT (application under test) and brownie points if you also have the tests running on mobile layouts. Think of reusability, order of tests, speed of the whole test suite, etc. We need to see that it can be used in the real world and not as a theoretical optimization.

Kick some ass!