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

fix: use avalanchego new *test packages #620

Merged
merged 7 commits into from
Aug 6, 2024

Conversation

ARR4N
Copy link
Contributor

@ARR4N ARR4N commented Aug 6, 2024

Why this should be merged

avalanchego was refactored and is already depending on one of the commits in this branch.

How this works

Magic 🧙 Also Find and Replace, but mostly magic.

How this was tested

Existing tests

@ARR4N ARR4N changed the title fix: use avalanchego new validatorstest package fix: use avalanchego new *test packages Aug 6, 2024
Copy link
Collaborator

@ceyonur ceyonur left a comment

Choose a reason for hiding this comment

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

should we also follow the same approach for testing packages in coreth?

changes LGTM

@ARR4N ARR4N merged commit 7cdd299 into master Aug 6, 2024
8 checks passed
@ARR4N ARR4N deleted the arr4n/use-avalanchego-test-pkgs branch August 6, 2024 12:57
@ARR4N
Copy link
Contributor Author

ARR4N commented Aug 6, 2024

should we also follow the same approach for testing packages in coreth?

changes LGTM

Yup. IMO there should never be test-helper code in production.

The only reason I used tags at the beginning instead of doing this refactor was because they were a quick fix.

oxbee pushed a commit to taurusgroup/coreth that referenced this pull request Nov 6, 2024
* fix: use new `statetest` package from AvalancheGo

* fix: use new `validatorstest` package from AvalancheGo

* chore: stop using deprecated `validatorstest.TestState`

* chore: bump `avalanchego` to commit with new test packages

* fix: update all `avalanchego/.../*test` usage

* fix: `scripts/versions.sh` in line with `go.mod`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants