onlydevelop / activity-v2 Goto Github PK

There is a chance of skipping the question if the Next button is always enabled. So, we want the student to attempt the question (maybe he need to give the correct answer, after trials) and only after that the next button will be enabled.

We need to create a build with tests so that, if the linting / tests fail the build will not succeed.

Questions are always asked in the same order as defined in the data.

This makes the initial questions are attempted more than the later questions if someone drops answering in between. Also it is not an interesting surprise which one will come next. Also this prepares better for questions as there is no sequence present.

So, let's randomize the questions.

We need to build the code when we are giving a PR against the master branch in Github.

https://docs.github.com/en/actions/automating-builds-and-tests/building-and-testing-nodejs

https://github.com/onlydevelop/activity-v2/new/master?filename=.github%2Fworkflows%2Fnode.js.yml&workflow_template=node.js

It would be nice to show the current number of question against total number of questions like:

Question: 1 of 14

Then, it will be easy to see how many question are completed / left.

The Unit Tests are not fixed. Please fix them and make them appropriate.

• The main component being QuestionComponent - we need to have the good coverage of Unit Tests for that component.
• Pages components are simple, so they could be some simple validation of the Subject name.
• NavbarComponent also needs the Unit tests for ensuring the exact number of routed menus which are present (not less and not more).

Add eslint with the default ruleset.

https://eslint.org/

The matching of answer is case sensitive. It may be case insensitive otherwise, it says wrong but shows the same answer with just case difference.

The landing page is blank which need to have some nice looking graphics and also probably the links to navigate to the respective subjects.

All questions are coming under same subject, which might be difficult to filter for term2 when first chapters in term1 are not in the exam.

It would be nice to redefine storing the data chapter wise. We can also think how UI may be changed (chapters coming in the nav bar or some accordian menu as left pane).

We can have some wireframe for discussion.

Choice for wireframe tools: https://www.interaction-design.org/literature/article/10-free-to-use-wireframing-tools?gclid=Cj0KCQjwtvqVBhCVARIsAFUxcRunj7J7NmhbxMZiOd5eqeVyg6cn4OJyGDGdSkXd7zcrTmTGXQ79-JIaAntWEALw_wcB