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

[CX_HARDENING] - Modernize and Audit View Sync Task Tests #3166

Closed
8 tasks
jparr721 opened this issue May 15, 2024 · 0 comments · Fixed by #3229
Closed
8 tasks

[CX_HARDENING] - Modernize and Audit View Sync Task Tests #3166

jparr721 opened this issue May 15, 2024 · 0 comments · Fixed by #3229
Labels
cappuccino cappuccino-sprint2 consensus-hardening Hardening the consensus protocol and adaquate testing.

Comments

@jparr721
Copy link
Contributor

What is this task and why do we need to work on it?

The View Sync Task tests have not been modernized to the new testing framework. It also only has a single test despite having a significant amount of logic that it performs. It is imperative that we add substantially more testing to this task.

What work will need to be done to complete this task?

  • - Modernize and improve the ergonomics of the View Sync task test by switching it to use the new testing framework.
  • - Evaluate the View Sync task to determine if enough of the code is covered.
  • - Permute the inputs and verify if the tests still pass.
  • - Clean up and reduce boilerplate within the test file.
  • - Add additional tests for the various cases that were not previously handled.

Are there any other details to include?

No response

What are the acceptance criteria to close this issue?

  • - Test is modernized
  • - New tests added if needed
  • - All tests pass.

Branch work will be merged to (if not the default branch)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cappuccino cappuccino-sprint2 consensus-hardening Hardening the consensus protocol and adaquate testing.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant