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

chore: fix system test for v2 #23328

Merged
merged 11 commits into from
Jan 14, 2025
Merged

chore: fix system test for v2 #23328

merged 11 commits into from
Jan 14, 2025

Conversation

aljo242
Copy link
Contributor

@aljo242 aljo242 commented Jan 10, 2025

Description

  • Clean up TestGetTxEvents_GRPCGateway fixing the test condition (expected and got were reversed)
  • Make it easy to run make test-system locally on your machine

Summary by CodeRabbit

Summary by CodeRabbit

  • Chores

    • Updated GitHub Actions workflow configuration
    • Modified system testing build and execution scripts
  • Tests

    • Refactored test case definitions for better readability
    • Updated test case parameters in transaction event tests

Copy link
Contributor

coderabbitai bot commented Jan 10, 2025

📝 Walkthrough

Walkthrough

The pull request introduces changes to the testing workflow and configuration for system tests. The modifications primarily focus on simplifying the build and test process for the simdv2 binary. The changes involve updating the GitHub Actions workflow, adjusting the Makefile for testing, and refactoring test case definitions in the tx_test.go file. The goal appears to be streamlining the testing approach for version 2 of the system.

Changes

File Change Summary
.github/workflows/v2-test.yml Removed COSMOS_BUILD_OPTIONS=v2 from the test-system job command
scripts/build/testing.mk - Simplified binary copying to directly use simdv2
- Explicitly set COSMOS_BUILD_OPTIONS=v2 for test execution
tests/systemtests/tx_test.go Refactored test cases for clarity in assertions and defined test cases explicitly

Possibly related PRs

Suggested Labels

C:server/v2, C:server/v2 appmanager

Suggested Reviewers

  • julienrbrt
  • tac0turtle
  • testinginprod
  • akhilkumarpilli

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 038872f and ff84535.

📒 Files selected for processing (1)
  • tests/systemtests/tx_test.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • tests/systemtests/tx_test.go
⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: tests (00)
  • GitHub Check: test-simapp-v2
  • GitHub Check: test-system-v2
  • GitHub Check: test-sim-nondeterminism
  • GitHub Check: test-integration
  • GitHub Check: build (amd64)
  • GitHub Check: Analyze
  • GitHub Check: golangci-lint
  • GitHub Check: Summary

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

@aljo242 aljo242 marked this pull request as ready for review January 14, 2025 00:53
@aljo242 aljo242 requested review from tac0turtle and a team as code owners January 14, 2025 00:53
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
tests/systemtests/tx_test.go (1)

411-413: Consider adding more specific assertions.

The test only verifies the length of transactions. Consider adding assertions for transaction ordering when testing ORDER_BY cases.

 				require.Equal(t, tc.expLen, len(txs))
+				if tc.expLen > 1 {
+					// Verify ordering based on height or time
+					for i := 1; i < len(txs); i++ {
+						prev := gjson.Get(txs[i-1].Raw, "auth_info.fee.amount.0.amount")
+						curr := gjson.Get(txs[i].Raw, "auth_info.fee.amount.0.amount")
+						if tc.url == "order_by=1" { // ASC
+							require.LessOrEqual(t, prev.Int(), curr.Int())
+						} else { // DESC
+							require.GreaterOrEqual(t, prev.Int(), curr.Int())
+						}
+					}
+				}
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b4e88cc and 038872f.

📒 Files selected for processing (3)
  • .github/workflows/v2-test.yml (1 hunks)
  • scripts/build/testing.mk (1 hunks)
  • tests/systemtests/tx_test.go (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
tests/systemtests/tx_test.go (3)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern tests/**/*: "Assess the integration and e2e test code assessing sufficient code coverage for the changes associated in the pull request"


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: tests (00)
  • GitHub Check: test-system-v2
  • GitHub Check: Analyze
  • GitHub Check: golangci-lint
  • GitHub Check: Summary
🔇 Additional comments (4)
scripts/build/testing.mk (1)

27-28: LGTM! The changes streamline v2 testing setup.

The modifications improve the testing workflow by:

  1. Directly using simdv2 binary instead of conditional logic
  2. Explicitly setting COSMOS_BUILD_OPTIONS=v2 for test execution

This change aligns well with the PR objective to fix system testing for v2.

tests/systemtests/tx_test.go (2)

347-351: LGTM! Well-structured test case definition.

The test case uses clear, descriptive field names and appropriate error handling expectations.


389-393: LGTM! Correct usage of ORDER_BY enum values.

The test cases now properly use the enum values (1 for ASC, 2 for DESC) instead of string literals, which aligns with the fix mentioned in the PR objectives.

Also applies to: 396-400

.github/workflows/v2-test.yml (1)

169-169: LGTM! Simplified workflow command.

Removing the environment variable from the workflow is correct since it's now handled within the Makefile target.

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

ACK. Muscle memory will still make me type/ctrl-r COSMOS_BUILD_OPTIONS=v2 make test-system tho 😅.

@julienrbrt julienrbrt added this pull request to the merge queue Jan 14, 2025
Merged via the queue into main with commit 69defb4 Jan 14, 2025
74 of 75 checks passed
@julienrbrt julienrbrt deleted the chore/fix-test branch January 14, 2025 22:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants