-
When the page loads, I want to see a text field with a button, so that I know I can submit search criteria.
-
When I click the submit button, I want the page to display the repositories of the username I submitted.
-
When a username does not exist, I want the page to display an error message, so that I know I need to try a different name.
Unit tests were run with Jasmine standalone, e2e testing was done manually in a web browser (Google Chrome: Chromium v 50).
Clone the repo (from mine or your own fork), cd into the folder, start a server in there with your preferred method, point your web brower address bar at your ServerAddress/html/index.html, play with it.
I have completed these job stories to the best of my ability. I have learned a lot during my work for this test, particularly about how to write Javascript without using libraries, which I had little experience of before. I now understand callbacks much better and feel more proficient with CSS, which I have not had much opportunity to work with in many of the exercises on the course. With this recently gained experience, I will build on it rapidly in the right environment and quickly make myself to an employer.
One thing I struggled with a little was test attrition. It became apparent that getting the asynchronous responses via callbacks meant not having an easy or obvious way to get them out of the callback function. I had to remove Response unit tests which were failing due to calls being made to a non-existent document, which I found myself struggling to mock properly. I had seen those tests passing previously with document calls extracted elsewhere, so felt able to delete them, but it was still frustrating to have to do so. TDD is, I feel, one of the most important methodologies I have learned during my course, so having tests to prove it is being followed is disappointing.
Whilst this tech test has taken almost all of the time allowed (a full weekend) to complete, it has also taught me a lot and I am now in a position to complete similar tasks much more quickly.
The main goal of this tech test is to create a client side web application that reproduces the screenshots below by using GitHub API .
We will only evaluate the client side code and the criteria will be based mainly on:
- Good use of pure Javascript language without external libraries and frameworks like jQuery, React...
- Clean HTML and CSS markup
- Clean, maintainable & easytoread
- Good architectural practices
- Investigate the github api calls for user and repos (for example: test them in the browser)
- Fork this repository & cd into the directory
- Launch the web application, for example with: python -m SimpleHTTPServer 1337
- Open the browser with http://localhost:1337/ and start coding!
- Adding Unit Testing. External libraries limitation doesn't apply here, you can use Jasmine, Karma...
The user can search a username of GitHub
If the searched username does exist: The searched user profile is displayed with all his repositories
If the searched username does not exist: An error is shown
