Skip to content

docs: E2E test plan for BN Verification plugin #908

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AlfredoG87
Copy link
Contributor

Reviewer Notes

Fixes #907

@AlfredoG87 AlfredoG87 changed the title initial test plan for verification docs: initial test plan for verification Mar 26, 2025
@AlfredoG87 AlfredoG87 changed the title docs: initial test plan for verification docs: E2E test plan for BN Verification plugin Mar 26, 2025
@AlfredoG87 AlfredoG87 self-assigned this Mar 26, 2025
@AlfredoG87 AlfredoG87 added the Design Issue/PR for feature design documents label Mar 26, 2025
@AlfredoG87 AlfredoG87 added this to the 0.8.0 milestone Mar 26, 2025
Copy link
Contributor

@Nana-EC Nana-EC left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, I think you noted one form might be going so the test plan might simplify even more correct?


- **Naive Tree Hasher:** calculates the root hash of the merkle trees in a synchronous manner and using a simple recursive algorithm.

- **Concurrent Tree Hasher:** calculates the root hash of the merkle trees in an asynchronous manner using a thread pool to parallelize the calculation as the blocks items are received and leafs are appended to the "merkle tree".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q: Is it important to note the logic of parallelization here in case it informs testing approach or is that an implementation not necessary?


## Test Scenarios

| Test Case ID | Test Name | Scenario Description | Expected Behaviour | Input | Output | Implemented (Y/N) |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note Test Case ID should be a unique string of sort, as a we want to note it in the code so that an E2E test can be mapped back to the plan

@georgi-l95 georgi-l95 added the Verification Plugin Issue related to Verification Plugin label Apr 2, 2025
Copy link

codecov bot commented Apr 2, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

@@            Coverage Diff            @@
##               main     #908   +/-   ##
=========================================
  Coverage     88.40%   88.40%           
  Complexity      723      723           
=========================================
  Files           132      132           
  Lines          3096     3096           
  Branches        230      230           
=========================================
  Hits           2737     2737           
  Misses          292      292           
  Partials         67       67           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@AlfredoG87 AlfredoG87 modified the milestones: 0.8.0, 0.9.0 Apr 3, 2025
@AlfredoG87 AlfredoG87 modified the milestones: 0.9.0, 0.10.0 Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Issue/PR for feature design documents Verification Plugin Issue related to Verification Plugin
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Verification Test Plan
3 participants