Skip to content
This repository has been archived by the owner on Feb 23, 2020. It is now read-only.

Latest commit

 

History

History
63 lines (42 loc) · 3.3 KB

LABTASKS.md

File metadata and controls

63 lines (42 loc) · 3.3 KB
Raw

Lab Tasks

  • Questions that you need to answer can be found in ANSWERS.md.
  • Tasks that specify work to do without a written response will be bulleted.

If you're ever confused about what you need to do for a given task, ask.

Table of Contents

Exploring the project

The structure of this project should be nearly identical to that of lab #3, and as such there really isn't much excitement in that department.

Exploring the server

The server is, for the most part, the same as it has been in the past two labs. The difference to look for here is in how the server gets the data it sends out in reply to requests.

Answer questions 1-7 in ANSWERS.md.

More Todos!

  • Re-implement the ToDo API, this time pulling data from MongoDB rather than from a flat JSON file.
  • When displaying the ToDos in your Angular front-end, make thoughtful decisions about whether work like filtering should be done in Angular or via database queries. For example, have the database filter out all the ToDos belonging to a single user, but let Angular filter by category, body, or status. Do at least some filtering on the database side of things.

Writing Todos to the Database

  • We have included an example of writing to the database with addUser functionality. Add to both the front-end and back-end to make it possible to add ToDos so that they appear both in your list and in the database.

Make it pretty

  • Use the Angular Material Design tools you've learned about to build a nice interface for accessing these APIs:
    • You must use at least two nifty Angular Material features from here!
    • There are many interesting features and documentation about how to use them - we encourage you to try several

Remember to test!

Test, test, and more test! Your project again should have tests. You should continue expanding upon your previous end-to-end test as well as implement Unit Test for both your client-side and the server-side.

Client-side testing

  • The gradle task runClientTestWithCoverage will be extremely useful to see how covered your client-side is by test.

  • Describe your E2E test coverage in a TESTCOVERAGE.md file. Update it when you add any additional end-to-end tests.

Server-side testing

  • Remember to add JUnit Test as you re-implement your ToDo API.

❗Pro-Tip: Test Coverage can be produced on IntelliJ as well! Go to to your server test folder and Right-click on the test folder and select Run 'All Test' with Coverage which will then provide a report of coverage in your server code in the side bar.

Additionally you can Right-click, select Analyze -> Generate Coverage Report... which will prompt you for an output directory and give you the option to view the report an HTML report in a browser.