We can't possibly say that we were slacking off here! After a tremendous amount of work, it's time to perform a final client-server test to ensure that everything is working as expected.

Run the application in debug mode by pressing F5 and wait from the Home view to load. Once done, click on one of the available quiz items; ensure that you choose one of the auto generated ones, because we need it to have questions, answers, and results:

Here's our beloved (yet still ugly) Quiz view. From there, left-click on the Edit button and see what happens:

We'll admit that it can definitely look a lot better. Yet it works! We got the quiz data, the questions list and the results list, which means that our QuestionListComponent and ResultQuizComponent are actually doing their job.

From here, we can click on the Add a new Question button to check out if the QuestionEditComponent is working as well:

Fill it with some sample data (as in the preceding screenshot), and then click on the Create the Question button to get routed back to the Quiz Edit view:

As expected, the new question is there; now we can use it to test the Edit mode of QuestionEditComponent. Left-click on the Edit button to its right to access it:

From here, we can test the answers-related component; the AnswerListComponent seems to be working fine already, so we can click on the Add a new Answer button and check out the AnswerEditComponent in Create mode:

From here, we can fill in the values and then issue the Create the Answer command; we'll get routed back to the AnswerEditComponent, where the AnswerListComponent should behave according to our actions:

So far, so good; now we should test the AnswerEditComponent in Edit mode to confirm that it also works. Once done, we can navigate backward using the Cancel button and delete what we just did to test the Delete functionalities provided by the answers and questions listing components. We should see the answer and the question disappear from the listings as soon as we confirm our choice.

Last but not least, we need to test the result-related components and repeat the same steps to ensure that everything is working fine on that part as well:

Since we're dealing with nullable values here, it's important to check for them too; in the preceding example, we're trying to create a new result without lower bounds--a null MinValue--and a MaxValue of 20. Our ResultListComponent should be able to handle it without problems, as we can see by clicking on the Create the Result button:

Here comes our custom N/A string. Now we just have to Edit the new result to test the ResultEditComponent in Edit mode; once done, Delete it and get ready for the next chapter.