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.

Sign up for GitHub

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

Jump to bottom

test: migrate remaining e2e tests to integration tests (backport #22364) #22381

Merged
merged 2 commits into from
Oct 27, 2024
Merged

test: migrate remaining e2e tests to integration tests (backport #22364) #22381

merged 2 commits into from
Oct 27, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 27, 2024

Description

Closes: #22358

  • Remove e2e tests completely and migrate remaining tests to integration tests.

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:

  • confirmed ! in the type prefix if API or client breaking change

  • targeted the correct branch (see PR Targeting)

  • provided a link to the relevant issue or specification

  • reviewed "Files changed" and left comments if necessary

  • included the necessary unit and integration tests

  • added a changelog entry to CHANGELOG.md

  • updated the relevant documentation or specification, including comments for documenting Go code

  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Bug Fixes

    • Removed the end-to-end testing job from the workflow, simplifying the testing process.
    • Deleted end-to-end test targets from the Makefile.
    • Removed the end-to-end test suite for lockup accounts.

  • New Features

    • Introduced a new integration test suite for lockup accounts.
    • Renamed existing test suites to reflect integration testing focus.

  • Documentation

    • Updated package declarations to indicate testing context.

  • Chores

    • Refactored test suite and method names for clarity and consistency.
This is an automatic backport of pull request #22364 done by [Mergify](https://mergify.com).

@akhilkumarpilli @mergify
test: migrate remaining e2e tests to integration tests (#22364)
f4607bd 
Co-authored-by: Julien Robert <[email protected]>
Co-authored-by: Marko <[email protected]>
(cherry picked from commit e37d71a)

# Conflicts:
#	tests/integration/tx/benchmark/service_test.go
#	tests/integration/tx/benchmark/testdata/tx_amino1.bin
#	tests/integration/tx/benchmark/testdata/tx_amino1.json
@mergify mergify bot added the conflicts label Oct 27, 2024
@mergify mergify bot requested a review from a team as a code owner October 27, 2024 14:21
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 27, 2024

Cherry-pick of e37d71a has failed:

On branch mergify/bp/release/v0.52.x/pr-22364
Your branch is up to date with 'origin/release/v0.52.x'.

You are currently cherry-picking commit e37d71ad2.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .github/workflows/test.yml
	modified:   scripts/build/testing.mk
	modified:   tests/Makefile
	deleted:    tests/e2e/accounts/lockup/lockup_account_test.go
	deleted:    tests/e2e/tx/service_test.go
	deleted:    tests/e2e/tx/testdata/tx_amino1.bin
	deleted:    tests/e2e/tx/testdata/tx_amino1.json
	renamed:    tests/e2e/accounts/base_account_test.go -> tests/integration/accounts/base_account_test.go
	renamed:    tests/e2e/accounts/lockup/continous_lockup_test_suite.go -> tests/integration/accounts/lockup/continous_lockup_test_suite.go
	renamed:    tests/e2e/accounts/lockup/delayed_lockup_test_suite.go -> tests/integration/accounts/lockup/delayed_lockup_test_suite.go
	new file:   tests/integration/accounts/lockup/lockup_account_test.go
	renamed:    tests/e2e/accounts/lockup/periodic_lockup_test_suite.go -> tests/integration/accounts/lockup/periodic_lockup_test_suite.go
	renamed:    tests/e2e/accounts/lockup/permanent_lockup_test_suite.go -> tests/integration/accounts/lockup/permanent_lockup_test_suite.go
	renamed:    tests/e2e/accounts/lockup/utils.go -> tests/integration/accounts/lockup/utils.go
	renamed:    tests/e2e/accounts/multisig/account_test.go -> tests/integration/accounts/multisig/account_test.go
	renamed:    tests/e2e/accounts/multisig/test_suite.go -> tests/integration/accounts/multisig/test_suite.go
	renamed:    tests/e2e/accounts/wiring_test.go -> tests/integration/accounts/wiring_test.go
	renamed:    tests/e2e/auth/keeper/account_retriever_test.go -> tests/integration/auth/keeper/account_retriever_test.go
	renamed:    tests/e2e/auth/keeper/app_config.go -> tests/integration/auth/keeper/app_config.go
	renamed:    tests/e2e/auth/keeper/keeper_bench_test.go -> tests/integration/auth/keeper/keeper_bench_test.go
	renamed:    tests/e2e/auth/keeper/module_test.go -> tests/integration/auth/keeper/module_test.go
	renamed:    tests/e2e/tx/benchmarks_test.go -> tests/integration/tx/benchmark/benchmarks_test.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	added by us:     tests/integration/tx/benchmark/service_test.go
	added by us:     tests/integration/tx/benchmark/testdata/tx_amino1.bin
	added by us:     tests/integration/tx/benchmark/testdata/tx_amino1.json

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@coderabbitai coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 27, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@julienrbrt julienrbrt merged commit 33d8838 into release/v0.52.x Oct 27, 2024
67 of 69 checks passed
@julienrbrt julienrbrt deleted the mergify/bp/release/v0.52.x/pr-22364 branch October 27, 2024 22:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@julienrbrt julienrbrt julienrbrt approved these changes

Assignees
No one assigned
Labels
Type: CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@julienrbrt @akhilkumarpilli