openedx / openedx/xblock-sdk

tests have unexpected side effects on each other

Open
#148 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
70
Forks
104
Avg merge
17h 46m
Merged PRs (30d)
14

Description

Steps to reproduce:

  • git checkout c4868e0de15d748a79f47fff3bf3cf217f87c318
  • tox -e py27-django111-- workbench/test/test_views.py # fails
E           PluginMissingError: xblockwithoutstudentview
  • tox -e py27-django111 -- workbench/test/test_scenarios.py workbench/test/test_views.py # works

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the two named test files, workbench/test/test_views.py and workbench/test/test_scenarios.py, using the py27-django111 tox commands in the report at commit c4868e0de15d748a79f47fff3bf3cf217f87c318. Compare the isolated and combined runs to identify the shared state causing PluginMissingError: xblockwithoutstudentview. Done means the tests no longer affect each other and the isolated command passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
django, python
Domain
testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.