This course uses a project-based approach to teach concepts of AdonisJS. The project in focus is a quiz app with an admin CMS.

tarball.tar.gz

APP_KEY

node_server

node_server_2

AdonisJS gives Nodejs developers a structured way to build full-stack apps and APIs with little boilerplate. In this course, you will learn how AdonisJS works by building
1. A quiz app
2. An admin CMS for the quiz app
Each chapter focuses on a core concept of AdonisJS using the app as a reference. 
The course covers
1. MVC architecture
2. Authentication
3. Authorization
4. Browser testing
At the end of this course, you'll be able to confidently build fullstack applications using AdonisJS.

Build a Trivia Quiz App with AdonisJS

## Our first tests
We will structure our tests such that each controller will contain tests for each method. Go ahead and delete example.spec.js, then run this
```bash
adonis make:test User -f
# output: create: test/functional/user.spec.js
``` 
Replace the content of user.spec.js with this
```js
"use strict";

const { test, trait } = use("Test/Suite")("User");

trait("Test/ApiClient");
trait("Auth/Client");

const User = use("App/Models/User");
```
### Testing registration
We'll follow the convention of using the present tense on test cases. Here, we are testing the register route and asserting that the status is 201. 
```js
test("registers a new user", async ({ client }) => {
  const response = await client
    .post(`/api/v1/register`)
    .send({
      email: "test-user@email.com",
      password: "some password",
      grade_system: "5",
    })
    .end();

  await response.assertStatus(201);
});
```
Kent C. Doods always says to ensure your test is working, feed it a wrong assertion. So we'll asset a 200 and run our tests.
```diff
- response.assertStatus(201);
+ response.assertStatus(200);
```
Now, run the tests

![Failing tests](https://cdn.hashnode.com/res/hashnode/image/upload/v1606589240762/a_flQjSDh.png)

Our tests said expected 201 to equal 200. We know that it is meant to be 201, so it means our test is working. Now return the assertion to its previous state and run the tests again.

![Screenshot from 2020-11-28 19-49-57.png](https://cdn.hashnode.com/res/hashnode/image/upload/v1606589426907/0gz68SOSW.png)

Huh 🤨? 400? Remember that the `register()` method in UserController.js returns errors for non-unique emails. We should probably write a test for that too eh? Change the email and run the test again.

![Passing registration test](https://cdn.hashnode.com/res/hashnode/image/upload/v1606589649700/u8QzKAO9p.png)

Hurray 🎊! It worked! That felt manual and isn't ideal. You know what will be better? A separate testing database which will be migrated and seeded before any tests run and revert the migrations after all the tests have run. 


# Our first tests
We will structure our tests such that each controller will contain tests for each method. Go ahead and delete example.spec.js, then run this
```bash
adonis make:test User -f
# output: create: test/functional/user.spec.js
``` 
Replace the content of user.spec.js with this
```js
"use strict";

const { test, trait } = use("Test/Suite")("User");

trait("Test/ApiClient");
trait("Auth/Client");

const User = use("App/Models/User");
```
## Testing registration
We'll follow the convention of using the present tense on test cases. Here, we are testing the register route and asserting that the status is 201. 
```js
test("registers a new user", async ({ client }) => {
  const response = await client
    .post(`/api/v1/register`)
    .send({
      email: "test-user@email.com",
      password: "some password",
      grade_system: "5",
    })
    .end();

  await response.assertStatus(201);
});
```
Kent C. Doods always says to ensure your test is working, feed it a wrong assertion. So we'll asset a 200 and run our tests.
```diff
- response.assertStatus(201);
+ response.assertStatus(200);
```
Now, run the tests

![Failing tests](https://cdn.hashnode.com/res/hashnode/image/upload/v1606589240762/a_flQjSDh.png)

Our tests said expected 201 to equal 200. We know that it is meant to be 201, so it means our test is working. Now return the assertion to its previous state and run the tests again.

![Screenshot from 2020-11-28 19-49-57.png](https://cdn.hashnode.com/res/hashnode/image/upload/v1606589426907/0gz68SOSW.png)

Huh 🤨? 400? Remember that the `register()` method in UserController.js returns errors for non-unique emails. We should probably write a test for that too eh? Change the email and run the test again.

![Passing registration test](https://cdn.hashnode.com/res/hashnode/image/upload/v1606589649700/u8QzKAO9p.png)

Hurray 🎊! It worked! That felt manual and isn't ideal. You know what will be better? A separate testing database which will be migrated and seeded before any tests run and revert the migrations after all the tests have run. 


Introduction to AdonisJS

Overview of Models, Views and Controllers in Adonisjs

Adding Authentication to an Adonis App

Building a Basic Admin Panel

Sending Notifications and Emails to Users in AdonisJS

Browser Testing

Conclusion

Final Assessment

Our first tests

Our first tests