Closed rltsystems closed 2 years ago
We need a detailed README that describes WHAT our project is and how it fulfills project requirements.
From the Project Document:
- MUST use test-driven development
This means that test cases are written BEFORE CODE
We will be using unit tests in class.
A story isn't complete until it passes all tests and is merged into master
Write out what the test should be, then stub out the methods. Read: https://developer.android.com/studio/test Read: https://developer.android.com/studio/test/espresso-test-recorder - MUST use proper JavaDoc style documentation - MUST use recycler views or list views https://codinginflow.com/tutorials/android/recyclerview-cardview/part-1-layouts-model-class - MUST use the Room persistence library 100% inflexible on this. Room will make this ‘good’ and good is always faster than easy. In general, whenever possible Android Architecture should be used https://codinginflow.com/tutorials/android/room-viewmodel-livedata-recyclerview-mvvm https://codinginflow.com/tutorials ← the single greatest Android resource on the planet. Alas the applicability of this has dropped as it is somewhat out of date… MUST use Git I would suggest one person clone this project, then everyone else pulling that project The individual contributions to the github repo will be a major part of the evaluation of this project. This means everyone MUST contribute. I don't want to hear "I didn't do anything because…" If you don't have a commit that shows some actually"
Reviewed and Completed.
rltsystems
commented
2 years ago rltsystems
commented
2 years ago
We need a detailed README that describes WHAT our project is and how it fulfills project requirements.
From the Project Document:
- MUST use test-driven development
This means that test cases are written BEFORE CODE
We will be using unit tests in class.
A story isn't complete until it passes all tests and is merged into master
Write out what the test should be, then stub out the methods. Read: https://developer.android.com/studio/test Read: https://developer.android.com/studio/test/espresso-test-recorder - MUST use proper JavaDoc style documentation - MUST use recycler views or list views https://codinginflow.com/tutorials/android/recyclerview-cardview/part-1-layouts-model-class - MUST use the Room persistence library 100% inflexible on this. Room will make this ‘good’ and good is always faster than easy. In general, whenever possible Android Architecture should be used https://codinginflow.com/tutorials/android/room-viewmodel-livedata-recyclerview-mvvm https://codinginflow.com/tutorials ← the single greatest Android resource on the planet. Alas the applicability of this has dropped as it is somewhat out of date… MUST use Git I would suggest one person clone this project, then everyone else pulling that project The individual contributions to the github repo will be a major part of the evaluation of this project. This means everyone MUST contribute. I don't want to hear "I didn't do anything because…" If you don't have a commit that shows some actually"