Technical Test

TodoMVC

Summary

The purpose of this exercise is to demonstrate your approach to quality from multiple angles.

There is no time limit for this test, but we expect most applicants to complete the requirements in roughly 3-4 hours.

If you make any assumptions about requirements, or use any online resources to solve a problem, please make note of these in your documentation or comments.

Your solution will be evaluated internally by your potential co-workers. You should expect a response from us within two business days.

Acceptance criteria

  1. Using the test automation framework of your choice, write automation tests for the TodoMVC application that cover the following scenarios:
    • Add a new todo item.
    • Remove an existing todo item.
  2. Come up with additional testing scenarios, writing automated tests for each.
  3. Ensure your submission contains a README.md file that includes:
    • Instructions on how to run your automated test suite.
    • Answers to the following questions:
      • If you joined a team of six engineers as the only engineer with testing experience and could implement any process you would like, how would you ensure that the team delivers high quality software?
      • If you were tasked with writing testing notes for this acceptance criteria (point 1 and 2), what would you write?
  4. Upload your submission to a public repository.
  5. Send the repository link to: amp HYPHEN tech HYPHEN test HYPHEN submissions HYPHEN group AT fairfaxmedia DOT com DOT au.

Developer notes

You may choose to run your tests against a public example TodoMVC application, or spin up the TodoMVC application locally. In either case, your submission should be well documented and reproducible by engineers evaluating your test.

Optional deliverables

  1. Tell us what you thought of the test and how long it took you to complete. This will help us improve the test over time!
  2. Tell us what else you might have done for the test if you had more time.