A Laravel test project to run through the basic concepts of Laravel.
- For this example, you can just use sqlite as a test database, or a local MySQL instance.
- Most application specific logic can be found within Laravel's
appdirectory. - All models should be located within the
App\Modelsnamespace. This is the official structure of Laravel as of Laravel 8. - Routing can be found underneath
routesand resources / views underresources. - Make a note of how long everything takes, if you struggle at any particular points also make a note of these.
- If you don't complete all points, it's not the end of the world.
-
Task 1
- Fork and pull the repository.
-
Task 2
- Establish a relationship between the
Questionnaireand itsQuestionmodels (already exists), and reverse. - Enforce eager loading so that a questionnaire always loads with its associated questions.
- Establish a relationship between the
-
Task 3
- Add a numerical
order_keyfield to the questions table, using migrations allowing the order of the questionnaire to be defined. - Ensure the questionnaire always loads the models with this new order applied.
- Add a numerical
-
Task 4
- Create seeders to seed 3 example questionnaires.
-
Task 5
- Commit your work and make notes of any pain points.
-
Task 6
- Using
php artisan serve, get a local development server running and ensure it all works. - Note: You will need to re-run
php artisan servewhen changes are made to the code-base.
- Using
-
Task 7
- Currently, we can access the questionnaire by navigating to /questionnaire/{id}, ideally, we want to
be able to navigate using a slug of the questionnaires name. Create a new migration to include a
slugfield and refactor the routing to load based on the slug provided. E.g. /questionnaire/test-project/
- Currently, we can access the questionnaire by navigating to /questionnaire/{id}, ideally, we want to
be able to navigate using a slug of the questionnaires name. Create a new migration to include a
-
Task 8
- Now we have a working questionnaire routing using a slug working, it's time to make a simple front-end interface. To do this, we'll need to use Laravel Controllers and routing, to output the questionnaire and its associated questions. It's up to you how you do this, you could choose to implement native HTML, Vue or React, Bootstrap or Tailwind.
-
Task 9
- Now that you have your front-end, we need to capture responses.
- To do this you'll need to create at least one new model with associated migrations.
- Create routing and appropriate controllers / controller models for capturing the data.
- Now that you have your front-end, we need to capture responses.
-
Task 10
- Write basic feature tests to ensure that your routes are capturing and handling the data appropriately.
-
Task 11
- Commit your changes and push, noting how long it all took and any particular pain points.