create tests for new assessor calling
Feature Description
we need tests for the new mechannism implemented in #28 (closed)
specifically those should test:
- that a member is notAvailable by default
- that a member who toggles themselves available is called
- that members who toggle themselves unavailable are not called
- that members that are moved around as a consequence of 3) are still called (test that the formerly last member is moved to the place of the member who untoggled themselves during 3)
this could looks something like this:
- somebody creates a new concept c as child of mew
- user x finishes an assessment in concept c
- another user creates an assessment in c and x is not called -> tests non-availability by default
- x toggles is availability and x is called -> test toggleAvailability
- a concept C2 with two parents (mew & C) is created
- user U (who is the first member in mew) sets his availability to notAvailable (-> see basicAssessment.js)
- user L (the last member in the mew-arra) togglesAvailability to notAvailable
- a user creates an assessment in C2 and
- x is called -> tests calling from multiple parents
- user U is NOT called -> tests removing
- user L is NOT called -> tests index-shifting
- and somebody else from mew is called
Motivation and Context
Possible Implementation
Related Issues/Tasks
- Depends On:
-
[ ]
- Enables: