Thank you for your interest in the role. So that we can get a feel for how you would approach technical testing at this time, it would be great if you could take a little bit of time to look at the following tasks.
In gaming, the back end services team provide GraphQL interfaces to consumers, providing valuable data on games and users to enable a great customer experience. What we are looking for you to do, is to test a scaled down version of one of our systems. We are looking for a lightweight and reusable test framework asserting that the data that is being requested is what we are expecting.
You can do this in whatever language, tool or framework that you desire but we will be looking for:
- Well structured code
- High quality of code
- Clear understanding of attributes and levels of abstraction that make up a good testing framework
The API that you are testing is a games catalogue. This image will provide you with 5 games already in the system. Each game must have an ID (generated by the system when created), a name, a slug and a supplier. You can inspect the list of suppliers and games by using the relevant queries that you can see in the docs when running the image. There is a games
, suppliers
, game
(gets a game depending on the id passed) and gameBySlug
. There are also two mutations for creating games (addGame
) and updating games (updateGame
) in the app.
The API in the image runs on port 4000.
The only file that we have added is a Makefile to store commands. In here there is already a stop and a logs command for the application. As you will see further down we are looking for you to add one command but feel free to add anything else that you wish.
You may add anything to your fork and enjoy!
As mentioned above, the language, framework or tools that you use are not restricted. The only things we are looking for is:
- A clear output of the tests that were run
- A simple way of running the tests
- Solid and comprehensive test coverage
Other considerations you might want to have a think about include:
- The ability to run your tests across platforms
- How you would reuse across multiple environments
If you have any issues with your code or any limitation of the application, please feel free to use pseudo code and comments to explain the thought process.
Please fork the repo and implement the following tasks...
Before the application can be run, the application will need to be started. Please fill in the start command of the make file to start the application. The only restriction here is, please name the container sbg-tech-test-app
.
Please test one of the queries. Choose one of the queries in the application and test it.
Similar to task 2, test one of the mutations.
If you feel like there is more that you would like to add, feel free to test the application more. There are bugs in the application by design so see how many you can find...
Once complete, please e-mail a link to your repo and instructions to run your tests to [email protected].