Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hide Playthrough Issues on Exploration Editor Stats Tab if Exploration is not Whitelisted #5947

Merged
merged 24 commits into from
Dec 6, 2018

Conversation

brianrodri
Copy link
Contributor

@brianrodri brianrodri commented Dec 6, 2018

Playthroughs should only be visible and recorded when a particular exploration is whitelisted. This allows us to continue working on changes and avoid recording potentially unsafe data until we're confident that Playthroughs are ready for general usage.

Testing Steps:

  1. Go to: Admin Page > Activities
    • Load Single Exploration 'Hola' (exploration id: '7')
  2. Go to: Admin Page > Config
    • Add element '7' to "The set of exploration IDs for recording issues and playthroughs"
    • Set "The probability of recording playthroughs" to 1 (i.e. 100%)
    • Save changes
  3. Play Hola exploration
    • Answer with 'Hola' and move to next card
    • Immediately navigate away from the exploration (and accept warning)
    • This should log an "Early Quit Playthrough"
  4. Go to: Hola's Exploration Editor > Stats Tab
    • Make sure Playthrough directive is visible and has one issue
  5. Go to: Admin Page > Config
    • Remove '7' from "The set of exploration IDs for recording issues and playthroughs"
    • Save changes
  6. Go to: Hola's Exploration Editor > Stats Tab
    • Make sure Playthrough directive is not visible
  7. Play Hola exploration
    • Answer with 'x' several times (~5s apart)
    • Navigate away from the exploration (and accept warning)
    • This should log a "Multiple Incorrect Answer Playthrough"
  8. Go to: Admin Page > Config
    • Add element '7' to "The set of exploration IDs for recording issues and playthroughs"
  9. Go to: Hola's Exploration Editor > Stats Tab
    • Make sure Playthrough directive is visible and still has exactly one issue
  10. Play Hola exploration
    • Answer with 'y' several times (~5s apart)
    • Navigate away from the exploration (and accept warning)
    • This should log a "Multiple Incorrect Answer Playthrough"
  11. Go to: Hola's Exploration Editor > Stats Tab
    • Make sure Playthrough directive is visible and has exactly two issues

@seanlip
Copy link
Member

seanlip commented Dec 6, 2018

@nithusha21 @BenHenning Please ignore the note on #5945. It's this PR (not that one) that should be merged for December.

Thanks!

@nithusha21
Copy link
Contributor

Hi @brianrodri thanks for the detailed testing instructions! However, I do not have admin permissions on the test server. Do you want me to test this locally?

Also, thanks for the PR, will make sure it is cherrypicked!

@seanlip
Copy link
Member

seanlip commented Dec 6, 2018

I've updated the test server config (and let @nithusha21 know)!

@seanlip
Copy link
Member

seanlip commented Dec 6, 2018

@brianrodri -- e2e tests are failing?

@codecov-io
Copy link

codecov-io commented Dec 6, 2018

Codecov Report

Merging #5947 into develop will decrease coverage by <.01%.
The diff coverage is 0%.

Impacted file tree graph

@@             Coverage Diff             @@
##           develop    #5947      +/-   ##
===========================================
- Coverage    45.48%   45.47%   -0.01%     
===========================================
  Files          517      517              
  Lines        30372    30378       +6     
  Branches      4568     4571       +3     
===========================================
  Hits         13814    13814              
- Misses       16558    16564       +6
Impacted Files Coverage Δ
..._editor/statistics_tab/PlaythroughIssuesService.js 1.69% <0%> (-0.16%) ⬇️
...head/pages/exploration_editor/ExplorationEditor.js 5.22% <0%> (ø) ⬆️
...exploration_editor/statistics_tab/StatisticsTab.js 2.17% <0%> (-0.03%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a7f2ae8...62b6d77. Read the comment docs.

@brianrodri brianrodri changed the title Hide Playthrough Issues when whitelist is not enabled Hide Playthrough Issues on Exploration Editor Stats Tab if Exploration is not Whitelisted Dec 6, 2018
@brianrodri brianrodri merged commit e93451b into oppia:develop Dec 6, 2018
@brianrodri brianrodri deleted the hide-playthroughs branch December 6, 2018 15:42
explorationId = newExplorationId;
explorationVersion = newExplorationVersion;
whitelistedExplorationIds = newWhitelistedExplorationIds || [];
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @brianrodri, I am a bit confused about this. Why do we need the || []? In other words why is newWhitelistedExplorationIds ever null?

nithusha21 pushed a commit to nithusha21/oppia that referenced this pull request Dec 15, 2018
…n is not Whitelisted (oppia#5947)

* Fix hola's multiple choice question.

* Pass whitelist to StatsTab

* Fix line-too-long

* Remove console

* always set whitelist to a list
nithusha21 added a commit that referenced this pull request Dec 15, 2018
* Hide Playthrough Issues on Exploration Editor Stats Tab if Exploration is not Whitelisted (#5947)

* Fix hola's multiple choice question.

* Pass whitelist to StatsTab

* Fix line-too-long

* Remove console

* always set whitelist to a list

* Small landing page changes based on feedback from Kefeh. (#5951)

* Fix error while displaying suggestion threads on learner dashboard page (#5965)

* fix error on learner dashboard page

* fix style
@nithusha21
Copy link
Contributor

Hi @brianrodri just leaving a note here. I have tested this PR on the test server, and everything works perfectly fine. Thanks a lot for the detailed instructions to test!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants