Special education: Add tests cases for current Bedford edge cases#2776
Merged
kevinrobinson merged 4 commits intoFeb 28, 2020
Conversation
…al-education-edge-cases
…al-education-edge-cases
Contributor
Author
|
selfie |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Who is this PR for?
Bedford educator
What problem does this PR fix?
There's some variation in manual processes for updating data about special education placement, previous identifications of disability, etc. in some upstream systems in Bedford. When Student Insights finds potentially conflicting information like this, it surfaces that in the UI so that folks notice and can bridge any communication gaps.
What does this PR do?
We're not yet sure if we want to keep this, make the "show conflicting information if its ambiguous how to interpret it" strategy more explicit and visible to users within Student Insights, or just address the underlying issues upstream. For now, this just adds two edge cases as test cases, verifying that these are working the way we have come to understand things in some other communication. If we decide on changes, we'll update these to reflect that.
Checklists
Which features or pages does this PR touch?
Does this PR use tests to help verify we can deploy these changes quickly and confidently?