brunnerant / sdp-project Goto Github PK

The answers may not be available at the end of the quiz. The participant should wait before accessing them.

It should support basic Request -> Response behaviour.
This interface is very important to allow the frontend and the backend to be uniformly handled.
There should also be a Request and Response class, that represent the ingoing and outgoing communications to the backend.

This class is used to store basic information about users, such as their username, their role, their category.

It should capture all the relevant data for a single question, including the format of the answer (e.g. single field, array, graph, ...).

This fragment should be able to dynamically instantiate the right type of answer fragment, depending on the type of the question.

• See how we manage sending answers to Firestore
• See how we represent answers

The QuizOverviewFragment contains all the questions of the quiz and is displayed at the left of the QuestionFragment in the QuizActivity. It contains the number and the title of each question. When we click on a question, it displays it in the QuestionFragment.
Notions to study: fragment, bundle

This issue is just here to count the hours that I spent this sprint.

First, I created the repo, the CI, CodeClimate, and all the toolchain.
I also added Spotless to our CI scripts, so that badly formatted code is not accepted.
I then fixed some issues with the Jacoco test reports not being generated correctly, and with
line endings in Windows, for my colleagues.
I also added caching to Travis to try and speed up the builds.

This issue is for now independent of the rest of the app.
We should start creating a Quiz class, and Question class to model quizzes and questions that are part of quizzes.
We should also start creating a simple activity that allows to view (not yet answer) a quiz.

• Link the quizzes to the database
• Add some dummy data to Firestore

actual: 13h for nbaehler and 13h nathan96g,
(at least)

The goal by the end of this sprint is to have a working login activity that makes some real requests to the firebase backend.

Ideally, we should also try to populate the database with some data, so that we have a working demo.

First, we should explore how firebase roughly works, and how we could integrate it in the app.
The first version of the backend should support simple challenge and response protocol for the login.
It means that #3 and #5 should already be done for this issue to be done.

Nathan worked 5h and Anthony 3h on this issue.

The login activity handles the login, and switches to the view role activity if the login was successful (for demo purposes). This issues depends on #3

Create EditMatrixFragment which shows a Matrix and which the possibility to have editable number of rows, columns, sign, decimal,...

Because we will be focuse on the user experience, ve have decided to put this user story aside.

This is one of the subtasks towards supporting quiz edition. Its goal is to create an overview of the quiz questions that allows to reorder, add, remove or edit questions. When editing or adding a question, this fragment should delegate to another fragment responsible for editing a single question.

Participants receive an ID by email and use it to connect to the app.
Users could access old quizzes without logging in.
There could be a "Corrector" type of user, that would be able to correct answers that were not automatically corrected.

Tasks #3 #6 #5 and #4 are responsible for this user story.

Friday evening meeting was made longer, because we absolutely needed to plan the global architecture of the app. We splitted the user stories into developer tasks and agreed on the global java architecture that we would use.

This fragment should handle question whose answer must be entered in a single field

Quiz Edition: Create pop up when create new question (transition from QuizActivity to EditActivity) with the choice of what kind of EditFragment one wants (Matrix1X1, Matrix3X3,...).

Add as well the possibility to create new ones such as Matrix42x42

Task #7 is addressing this issue.

We had estimated 3h where Anthony and Nathan would work together to debug, it took 5 hours for both. They received help from Nicolas and Antoine.

We grouped many issues because we did them all in this PR.

• Finish email/password login, solve bugs, test
• Automatic log in if user is already logged in.
• Improve user database structure (users have a list of their quizzes, etc.), create user in database when sign up

actual 16h: Anthony's work. This PR was longer to finish than I imagined!

actual 8h: Nathan's work. I did not plane at first to work on this pr, that is why i did not make an estimation of work time.

Makes to "homepage" more sophisticated and modular.

I sanitized the token inputted by the user. Now, only a 20 characters alphanumeric string is accepted.
I also added more test questions in the mock database, and the QuizOverview now displays the titles of the questions.

There are some things that the linter complains about etc. As no one wanted to do the changes theses things in their specific PR, I'm going resolve them with a separate PR.

This task is one of the subtasks towards supporting quiz edition. It should handle the edition of a single question. This includes editing the title and the question itself, and the answer format as well.

This is not a new feature per se, but rather combining, cleaning up, and testing more thoroughly the code from issue #30.