alexstojda / soen390 Goto Github PK

Create the Distraction Free mode UI, with the following features:
A search bar at the top;
A web view for the article.

No bottom navigation bar, settings page, etc should appear.

Create the navigation item to exit the Distraction Free mode.

• The user shall pull the article down, displaying a pop up header;
• The pop up header shall have text saying "Exit Distraction-Free mode", and a left-pointing arrow;
• Upon exiting, the user shall return to the same article, in the regular article-viewing mode.

Describe the bug
Due to the article being really named "Concordia University (Montreal)", instead of "Concordia University", the user never gets to the winning state.

To Reproduce
Steps to reproduce the behavior:

1. Start The Game with "Concordia University"
2. Travel to the Concordia University page
3. Notice that you did not win.

Expected behavior
The user should win the game when traveling to that page.

Description: Unless the user manually goes into their phone setting and enables camera permission, the app will crash when using wiki walky

To Reproduce:

Steps to reproduce the behavior:

1. fresh download app
2. enable wiki walky in settings
3. go to an article
4. app will crash

Expected behavior:
The app should prompt user to enable the camera hardware

Environment:
Reproduceable on all android devices on all recent versions of android

Architecture diagram of the application in its current state (IE Before we start adding features)
Examples from previous project: https://github.com/amawai/android-wikipedia-390/wiki/Architecture-Recovery

Elevator pitch description at a high level for the release summary.

Add the Code Style Guide to the project wiki

Bug description
Certain phones fail the test while others do not.

To Reproduce
Run test and see if your phone has Chinese characters after the first initial skip.
If so, your device will fail the test.

STORY CHECKLIST

• MockUps have been made an presented to the TA
• Story has been broken down into sub-tasks
• Story tasks have appropriate estimates (using Fibonacci)

Describe the user story
As a user, I want to be able to browse and search through articles without any history being produced.

Describe alternatives you've considered
Initially, the design would have the icognito switch in the article UI. Instead, it was decided to have the toggle as a setting on the settings page.

Setup all relevant checks in the CI Pipeline

Describe the bug
Permission to enable camera was added to Wikiwalkey which caused the espresso test to no longer work.

To Reproduce
Steps to reproduce the behavior:
run Wikiwalkey enable espresso test

Expected behavior
should run

STORY CHECKLIST

• MockUps have been made an presented to the TA
• Story has been broken down into sub-tasks
• Story tasks have appropriate estimates (using Fibonacci)

Describe the user story
As a user, I want to be able to read articles while also seeing what is ahead of me while walking.

Describe alternatives you've considered
No alternatives for this story were considered.

Additional context
Essentially, the application background should be replace with the output of the camera so that the user can see where they are walking while reading an article.

1 Paragraph description of the CI setup.

Describe the bug
Checkstyle checks do not run in circleci

To Reproduce
Steps to reproduce the behavior:

1. Trigger build in circleci, style checks are not executed.

Setup the repository with all continuous integration checks as well as define any standards and style guidelines.

Sprint 2 is complete and the feature/planning for Sprint 3 has been accepted.

You seem to have a good handle on the App and your plan for the future sprints seems good and scalable. Your current work is good, keep it up.

Keep putting emphasis on planning and review activities, they will still be worth a decent amount in future releases.

Keep on making sure that every commit has an issue linked, so far it looks alright, with a few commits without an issue here and there.

Make sure to keep producing mockups as needed (fixed versions are much better).

Make sure everyone has mostly equal code to their name (both test code and implementation code), this will become more strict now that we are entering release 2 and we expect more code and less planning overhead.

Please try to be more timely with your release for release 2 (getting me the report, not modifying the repo after the release is tagged for mockups/issue priority/risk). We will be strict next release.

If you have any problems let me know as early as possible (especially with Espresso) and I will try to find solutions with you.

Oh you can also close the sprint :D

STORY CHECKLIST

• MockUps have been made an presented to the TA
• Story has been broken down into sub-tasks
• Story tasks have appropriate estimates (using Fibonacci)

Describe the user story
As a user, I want to be able to read an article without being distracted by the many other UI elements available.

Describe alternatives you've considered

• Simply just removing some UI components but not all

Additional context
Add any other context or screenshots about the feature request here.
Mockup: https://imgur.com/fwKBz1E

Class diagram of the application in its current state, with focus on the classes we currently believe to have the biggest impact on the introduction of our new features (IE Before we start adding features)
Examples from previous project: https://github.com/amawai/android-wikipedia-390/wiki/Architecture-Recovery

Create a Card on the "Explore" feed to enter a distraction free mode

STORY CHECKLIST

• MockUps have been made an presented to the TA
• Story has been broken down into sub-tasks
• Story tasks have appropriate estimates (using Fibonacci)

Describe the user story
As a user, when I am reading an article and want to select a random article related to the current one to read next, I can shake my phone to select a new one.

Describe alternatives you've considered
We considered adding the shake2shuffle feature to the existing "Randomizer" feature, but that would not have enough complexity to warrant a full story, so we chose this approach instead.

Sprint 3 is now complete you can close any unclosed issues if there are any.

Good work completed, make sure to finish off the features that you started in sprint 3, if you end up with a bit of extra time, you can try to add a bit to each or add a small spike feature into sprint 4.

Priority, risk, and points appear well distributed, overall decent planning. Make sure everyone has the opportunity to work as equally as possible.

Mockups are good, keep making sure to have the plan and mockups ready in all future sign-offs as well.

Make sure to have running Espresso (UI) tests ready for sprint 4 sign-off so that you can show me that they work. Be sure to spend some time making good unit tests so that you can get decent code coverage, as well as show that you have thought about any edge cases.

Don't forget to plan out release 3 and have the plan ready (including mockups) for the sprint 4 sign-off.

Overall good, keep it up.

Populate all remaining iteration data in the release summary document.

• Team Member Story Points
• Velocity Chart
• Code (top 2 most important files that you wrote or changed (full path). see report template)
• Testing and CI (See report template)
• Review infrastructure section to ensure all info is present

Describe the bug
The espresso tests fail to run locally.

Additional context
Need to evaluate running them in firebase

Write an Espresso test for The Game. It should test that the link click increments the counter, that the Toast is visible on the Winning page, and that the surrender button works.

STORY CHECKLIST

• MockUps have been made an presented to the TA
• Story has been broken down into sub-tasks
• Story tasks have appropriate estimates (using Fibonacci)

Describe the user story
The Idea of the game is the user chooses a destination page and must get to that page using as few jumps through related articles as possible. Hopefully, the user will learn something along their journey.

Describe alternatives you've considered

• No alternatives were considered.

Additional context
Add any other context or screenshots about the feature request here.
Mockups - https://imgur.com/tbTczTf

• Menu item (somewhere) to open the Game Start UI
• View to select destination and start the game

The release summary for iteration 1 using this template

Describe the bug
Code Coverage Reports are not being generated

To Reproduce
Steps to reproduce the behavior:

1. Run tests

Expected behavior
Coverage reports should be generated when unit tests are run

Setup everything related to the GitHub repo

• Clone release from main application and create new repo (don't fork)
• Add all users to the repository
• Create issue templates
• Create PR templates

• Research possible methods of parsing article text
• Implement best-chosen method

Find a way to make an espresso test that can shake during test or open the related article view during test.