-
Notifications
You must be signed in to change notification settings - Fork 7
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
mark-scan: Instructions for early ballot removal #4681
Conversation
e5a2835
to
952eaa8
Compare
952eaa8
to
0c02a6b
Compare
@@ -1 +0,0 @@ | |||
./build/assets/index.c1222e2b.js:31135 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
codemod
util file that was previously committed by accident
0d43332
to
8fc83c1
Compare
8fc83c1
to
1798ba2
Compare
// move auth entirely to the backend. | ||
// https://github.com/votingworks/vxsuite/issues/3985 | ||
stateMachineState !== 'accepting_paper' && | ||
stateMachineState !== 'not_accepting_paper' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that we've seen this is a consistent pattern for any state that changes auth in the backend, IMO we should bump the priority of #3985 ahead of adding any additional states with auth changes @arsalansufi @jonahkagan @mattroe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense! I brought the issue up to the medium pri section on the VxMarkScan board. (I don't have a great sense of which issues would require "adding any additional states with auth changes")
@@ -283,6 +296,45 @@ test('voting flow happy path', async () => { | |||
await waitForStatus('not_accepting_paper'); | |||
}); | |||
|
|||
describe('removing ballot during presentation state', () => { | |||
test('is a no op if USE_MOCK_PAPER_HANDLER=true', async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need this to no-op because we detect ballot removal when the NO_PAPER_ANYWHERE
event is fired, and paper handler status always reports NO_PAPER_ANYWHERE
when using mock paper handler.
Overview
#4542
Gives instructions to the voter when the ballot is removed during the presentation stage. On mark-scan the ideal path is for the voter to use the interface to confirm their ballot is correct, which causes the app to pull the paper back in and cast it to the rear box. But it's likely that some voters will remove the ballot during the presentation stage, especially if they realize other voters are casting their HMPBs at a precinct scanner.
In the case of early removal we should give instructions to cast at a precinct scanner rather than just ending the session.
Demo Video or Screenshot
Changes start at 0:20
IMG_4800.MOV
Testing Plan
Checklist