This assessment is individual and you will be working on it for 3 hours. It's advisable to familiarize yourself with the recommended resources (details below) before the assessment.
It is not necessary to complete the assessment in order to pass. You need to demonstrate a good understanding of the code you are working with and to be able to implement features at the speed of a junior developer.
In this assessment you will:
- Use test-driven development
- Work with a third party API
- Demonstrate mastery of all parts of the Rails stack
- Demonstrate mastery of Ruby throughout the process
- Commit every 15 minutes to track your progress (details below)
The intent of this assessment is to demonstrate a solid working understanding of the following:
- Producing an API
- Consuming an API
- Testing an API
- Sending data from a form for data not stored in a database.
- Storing data in a Rails Session
- Using ActiveRecord to filter data
- Core concepts covered in the previous two Modules
In addition, we expect you to:
- Be able to explain all lines of code in your project
- Be able to interpret and implement user stories in a Rails project
- Be able to read, understand and refactor existing code
- Be able to use external resources in the problem solving process (ie: Google, Docs etc)
NOTE: only some of these topics will be included in the assessment.
- As you work, you should:
- Commit and push your code every 15 minutes.
- Reference external public resources (ie: Google, Ruby API, etc)
- Use the tooling most comfortable to you (Editor/IDE, testing framework, support tools like Guard, etc)
- As you work, you should not:
- Copy code snippets
- Seek live support from individuals except instructors
- Review implementations on old projects and/or notes
To better follow your progress over the three hours we expect that you commit every 15 minutes regardless of where you're at. Try to be as descriptive as possible in your commit messages and sum up briefly how you spent the time.
Set up a new project titled module_3_assessment associated with your Github account.
You will build on Storedom. Make sure you setup the project before the assessment.
NOTE: Delete Gemfile.lock before you bundle to avoid version conflicts.
$ git clone git@github.com:turingschool-examples/storedom.git
$ cd storedom
$ rm -rf Gemfile.lock
$ bundle
$ bundle exec rake db:{create,setup}
$ git remote add upstream git@github.com:YOUR-GITHUB-USERNAME/module_3_assessment.gitMinitest/Capybara is already set up in the project. Run rake test to see one integration test passing. If you prefer to work with RSpec, please remove the test/ directory and set up RSpec in your project before the assessment.
The night before the assessment you will be asked to get keys for the API you will be working with.
Once you have your project ready to go, commit and push to your remote repo to confirm everything is set up correctly using something similar to the following:
$ git add .
$ git commit -m "Complete setup for M3 assessment."
$ git push -u upstream masterThese are recommended resources to look through before the assessment, and/or use during the assessment.
- Request libraries such as Faraday or Net::HTTP
- VCR
- Ruby Docs
- ActiveRecord Query Methods like
.where,.find_by,.joins,.includes. - ActiveRecord calculations
- Rails Docs
Subjective evaluation will be made on your work/process according to the following criteria:
- 4: Developer writes code that is exceptionally clear and well-factored
- 3: Developer solves problems with a balance between conciseness and clarity and often extracts logical components
- 2: Developer writes effective code, but does not breakout logical components
- 1: Developer writes code with unnecessary variables, operations, or steps which do not increase clarity
- 0: Developer writes code that is difficult to understand
- 4: Developer is able to craft Rails features that follow the principles of MVC, push business logic down the stack, and skillfully utilizes ActiveRecord to model application state. Developer can speak to choices made in the code and knows what every line of code is doing.
- 3: Developer generally writes clean Rails features that make smart use of Ruby, with some struggles in pushing logic down the stack. The application displays good judgement in modeling the problem as data. Developer can speak to choices made in the code and knows what every line of code is doing.
- 2: Developer struggles with some concepts of MVC. Developer is not confident in what every line of the code is doing or cannot speak to the choices made.
- 1: Developer struggles with MVC and pushing logic down the stack
- 0: Developer shows little or no understanding of how to craft Rails applications
- 4: Developer excels at taking small steps and using the tests for both design and verification. All new lines of code are tested.
- 3: Developer writes tests that are effective validation of functionality. Most new lines of code are tested.
- 2: Developer writes tests. Most new lines of code are tested but they aren't effective at testing for functionality and value.
- 1: Developer is able to write tests, but most new lines of code are not tested.
- 0: Developer does not use tests.
- 4: Developer is able to implement solutions at the speed of a developer.
- 3: Developer is able to implement solutions at the speed of a junior developer.
- 2: Developer is able to implement solutions at the speed of an apprentice.
- 1: Developer struggles to implement solutions at the speed of an apprentice.
- 0: Developer is not able to implement basic functionality.
- 4: Developer commits every 15 minutes
- 3: Developer commits almost every 15 minutes
- 2: Developer does not commit regularly
- 1: Developer has poor git workflow and does not commit regularly
- 0: Developer committed once