-
Notifications
You must be signed in to change notification settings - Fork 0
Milestones
List view
For the final deadline: - Multiple unit tests (even if they are silly). - Multiple behavioral tests. Test the core functionality of the app. - In your Readme.md file add a Testing section which lists - the commands/instructions one must type to run your tests - the directory (or filename regexep) where all your tests are located - Add an Issue titled "Testing Video" to your repo and and put in there a video, or more, showing how the tests run. - Optionally, setup a continuous integration service, like travis to automatically run your tests.
Overdue by 1 year(s)•Due by April 28, 2025•1/1 issues closedTo release your code you will: - Create a git tag named v1.0 on the commit that marks the release: git tag v1.0 - Push tags to GitHub: git push --tags. Once pushed to GitHub you will find a Release called v1.0 in your repo. If you can't get tags to work just create the Release called v1.0 with GitHub. If you have a mobile/desktop app you will: - Upload your binary (.apk .exe, etc.) to the Release.
Overdue by 1 year(s)•Due by April 28, 2025•7/7 issues closed- Create an Issue in your repo titled "Final Demo" and either upload your video into the Issue or add a link to the video hosted at youtube (or similar). - Assign the Issue to @josemvidal
Overdue by 1 year(s)•Due by April 28, 2025•1/1 issues closedAdd an Issue with title "Website" and assign it to @josemvidal. It should have: - The URL of your website. The website should have the video/placeholder embedded in it, and the screenshots embedded in it, as described above. - At least 3 pretty screenshots of your app should be featured in the website.
Overdue by 1 year(s)•Due by April 24, 2025•1/1 issues closedWhen testing the other group's project you need to: - Add every bug you find to their Issues list. Use screenshots whenever useful. Explain clearly how to reproduce the problem. - When you are done testing, tell the other team. When being tested you will assign labels to each issue the testers submit. Namely: - Add the qa label to all their Issues. This is a new label to help us distinguish the other teams' Issues from yours. - If it is a bug, give it the bug label. Add it to the 1.0 Milestone. - If it is not exactly a bug, but something that really should be added, you can add an issue about it with the enhancement label. - If it is a duplicate of an existing Issue, write a comment pointing to the Issue you want to keep, add the built-in duplicate label and close it. - If you decide that fixing it is outside the scope of the project then add the wontfix label, explain why, and close it.
Overdue by 1 year(s)•Due by April 20, 2025To release your code you will: - Create a git tag named v0.9 on the commit that marks the release: git tag v0.9 - Push tags to GitHub: git push --tags Once pushed to GitHub you will find a Release called v0.9 in your repo. If you can't get tags to work just create the Release called v0.9 with GitHub. If you have a mobile/desktop app you will: - Upload your binary (.apk .exe, etc.) to the Release.
Overdue by 1 year(s)•Due by April 6, 2025•30/30 issues closedTo make a Release you will: - Create a git tag named v0.5 on the commit that marks the release: git tag v0.5 - Push tags to GitHub: git push --tags. Once pushed to GitHub you will find a Release called v0.5 in your repo. If you can't get tags to work just create the Release called v0.5 with GitHub. If you have a mobile or desktop app you will: - Upload your binary to the Release: .apk for Android, .exe for Windows. If you are targeting iOS then you will be using TestFlight, you must send us an invite by the deadline.
Overdue by 1 year(s)•Due by March 2, 2025•28/28 issues closedFor the first deadline: - Have at least one unit and one behavioral test in your repo. Typically in a tests folder. - In your Readme.md file add a Testing section which lists - the commands/instructions one must type to run your tests - the directory (or filename regexep) where all your tests are located. - Add an Issue titled "Testing Video" to your repo and and put in there a video, or more, showing how the tests run. - Once your tests are committed, create a git tag named v0.2 on the commit that marks the release: git tag v0.2 - Push tags to GitHub: git push --tags.
Overdue by 1 year(s)•Due by February 2, 2025•1/1 issues closed