The aim of this exercise is to demonstrate your problem solving and understanding of Python by implementing something found in every unit testing tool - an "assert_equals" method.
- Fill in the "assert_equals" function provided such that it will correctly compare the "expected" and "actual" parameters.
- The parameters could be of any conceivable Python type, but we only expect you to handle primitive data types (e.g. strings and numbers) and simple arrays to start with
- You can work with the code we've given you, or rewrite bits if that works best for you. You may add extra functions and files as you see fit.
- Credit will be given for approach, correctness, clean code, and testing.
- We don't expect you to progress to dealing with more complex data types than those shown here.
- We respect your time, and - assuming you are already familiar with Python - we do not expect you to spend more than an hour doing this exercise.
- Please do not use external libraries (except for a testing library)
- You may of course use any resources you like to assist you with specific techniques, syntax etc - but please do not just copy code.
- Please don't share this exercise with anyone else :)
- We've written an initial implementation and associated test in pytest, which is our testing library of choice. You may use a different library if you wish.
| Expected | Actual | Result |
|---|---|---|
| "abc" | "abc" | No error |
| "abcef" | "abc" | Raises error with message 'Expected "abcef" but found "abc"' |
| 1 | 1 | No error |
| 1 | 2 | Raises error with message 'Expected 1 but found 2' |
| 1 | '1' | Raises error with message 'Expected type int but found type str' |
| ["a", "b", "c"] | ["a", "b", "c"] | No error |
| ["a", "b"] | ["a", "b", "c"] | Raises error with message 'Expected list length 2 but found 3' |
| ["a", "b"] | ["a", "d"] | Raises error with message 'Expected "b" but found "d"' |
pipenv install --dev
pipenv run pytest -vvs
- The pairing exercise will be conducted remotely via Google Meet. If you haven't used this before, we recommend getting comfortable with it in advance. In order to share your screen, you may have to update your browser settings and restart the browser. Doing this in advance will save us time and hassle during the pairing session.
- Please have your chosen text editor or IDE ready to go, with the code open on your screen. You should be able to run the tests.
- You'll meet two of our engineers. As well as pairing, it will be an informal opportunity to get to know them and ask questions about working at Fluidly.
- We allow an hour for the session. Usually that's about 5 minutes of introductions, 45 minutes of coding, and 10 minutes for questions at the end.
- You'll share your screen with us. You'll talk us through the code you've written so far. Then we'll work together to add new functionality.
- We usually start by implementing object comparison. If time allows, we'll move on to comparing more complex objects.
- We will insist on practising test driven development (TDD) with you.
- As well as assessing your Python and TDD skills, we'll be looking for excellent communication skills, initiative, willingness to learn, and ability to cope under pressure.
- You can ask us questions at any time during the test.
- We know that it's difficult to write your best code while being watched by two people you don't know. We don't expect perfection, and will do our best to make the experience as comfortable and enjoyable for you as we can. Please let us know if you'd like us to make any adjustments.