delivery-engineer-worktest

Setup

1. Install node package manager.
2. Execute npm run launch-app on the command line.
3. Open a browser to http://localhost:3000/ to confirm that the application is running.

For both of these exercises, it may be useful to review TestCafe's documentation on debugging.

Exercise 1: Failure Diagnostics

Open a new command line and execute npm run failure-diagnostic-exercise.

Imagine that this is an end-to-end test for a real web application. Assume that it is intended to test the following workflow:

1. Fill in the title of the research proposal.
2. Fill in all required fields of the principal investigator section.
3. Fill in all required fields of the co-investigator section.
4. Select yes/no to the institute member and funding support questions.
5. Add a letter of support.
6. Check all but one item on the research application checklist.
7. Agree to the terms of service and provide an electronic signature.
8. Try to send the application but expect that the user is not able to continue due to a missing required field.
9. Check off the remaining checkbox.
10. Send the application, expect that the submission is successful.

The test is already written to complete this workflow. However, when you run the test now, you will see that it fails before it has completed this workflow. Your job is to diagnose why it's failing.

If the failure represents a problem with the website, i.e. a bug that should be reported to the website administrator, put a description of the bug in the bug_report.txt file. Once you discover a bug, you are done with this exercise.

If the test fails because the test itself is not properly configured, edit the test code in tests/failure-diagnostic-exercise-test.js such that the test passes and can continue the workflow. Note: the point is not to change the workflow in any way, but to infer whatever action the test is trying to perform and fix whatever is preventing it from doing so.

When you rerun the test, if further points of failure are exposed, check if it's a bug, otherwise fix the test code. Repeat until you hit a bug or the test passes.

There is a correct answer to this exercise. You should spend no more than 30 minutes on it.

Exercise 2: Assertions

Open a new command line and execute npm run assertions-exercise. Watch the test run. It should pass.

Open tests/assertions-exercise-test.js in your preferred IDE. You'll notice that the test code has no assertions. Add assertions that would that make the test more robust, i.e. expectations that would fail if there were bugs or issues with the UX.

Here is the documentation for assertions in TestCafe.

There is not a definite set of right answers to this exercise. The goal is for you to demonstrate the critical thinking skills of a QA engineer in identifying what should be tested. The assertions you write should expose bugs and cause the test to fail where a test with only click() and typeText() events would pass.

You should spend no more than 1.5 hours on this exercise.

Submission

Create a branch with the following naming scheme: <First_Initial>_<Last Name>_<Month>_<Day> For example: a_smith_09_02 Push to remote and raise a PR. This will signal to us that you have completed the exercise, and we will be in touch with next steps.