Overview

The PR adds the UI to give the diagnostic test from the diagnostic test player page. And, based on the performance in the test, 0, or 1, or 2 topics were recommended.

Essential Checklist

• The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• The linter/Karma presubmit checks have passed locally on your machine.
• "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)
  • This lets reviewers restart your CircleCI tests for you.
• The PR is made from a branch that's not called "develop".

Proof that changes are correct

Updated screenshots

Existing exploration editor and player

Existing practice session

PR Pointers

• Make sure to follow the instructions for making a code change.
• If you need a review or an answer to a question, and don't have permissions to assign people, leave a comment like the following: "{{Question/comment}} @{{reviewer_username}} PTAL". Oppiabot will help assign that person for you.
• For what code owners will expect, see the Code Owner's wiki page.
• Make sure your PR follows conventions in the style guide, otherwise this will lead to review delays.
• Never force push. If you do, your PR will be closed.
• Some of the e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.