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: Fix app.Test() auto-failing when a connection is closed early #3279

Merged
merged 6 commits into from
Jan 13, 2025

Conversation

grivera64
Copy link
Member

@grivera64 grivera64 commented Jan 12, 2025

Description

This PR fixes the bug where app.Test() auto-fails by returning testConn is closed if the underlying connection is closed during a fiber.Handler. Namely, c.Drop() falls under this category, as it calls c.RequestCtx().Conn().Close().

To fix this, we do not return an error if the error matches with errTestConnClosed. If there was truly an error, it should return as ErrTestGotEmptyResponse due to an empty response (which should be expected when c.Drop() is called).

Fixes #3278

Changes introduced

List the new features or adjustments introduced in this pull request. Provide details on benchmarks, documentation updates, changelog entries, and if applicable, the migration guide.

  • Benchmarks: Describe any performance benchmarks and improvements related to the changes.
  • Documentation Update: Detail the updates made to the documentation and links to the changed files.
  • Changelog/What's New: Include a summary of the additions for the upcoming release notes.
  • Migration Guide: If necessary, provide a guide or steps for users to migrate their existing code to accommodate these changes.
  • API Alignment with Express: Explain how the changes align with the Express API.
  • API Longevity: Discuss the steps taken to ensure that the new or updated APIs are consistent and not prone to breaking changes.
    • This PR is a step to ensure that app.Test() is working as expected for new corner cases introduced in v3.
  • Examples: Provide examples demonstrating the new features or changes in action.

Type of change

  • Enhancement (improvement to existing features and functionality)

Checklist

Before you submit your pull request, please make sure you meet these requirements:

  • Followed the inspiration of the Express.js framework for new functionalities, making them similar in usage.
  • Conducted a self-review of the code and provided comments for complex or critical parts.
  • Updated the documentation in the /docs/ directory for Fiber's documentation.
  • Added or updated unit tests to validate the effectiveness of the changes or new features.
  • Ensured that new and existing unit tests pass locally with the changes.
  • Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
  • Aimed for optimal performance with minimal allocations in the new code.
  • Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Please use emojis in commit messages for an easy way to identify the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md

@grivera64 grivera64 requested a review from a team as a code owner January 12, 2025 00:27
@grivera64 grivera64 requested review from gaby, sixcolors, ReneWerner87 and efectn and removed request for a team January 12, 2025 00:27
Copy link
Contributor

coderabbitai bot commented Jan 12, 2025

Walkthrough

The pull request introduces enhancements to the error handling in the app.Test() method of the Fiber framework. A new error variable ErrTestGotEmptyResponse is defined and utilized within the Test method to replace hardcoded error messages. Additionally, modifications are made to various test functions to improve error assertions, ensuring they check for specific error types. These changes aim to provide clearer and more maintainable error handling, particularly when dealing with connections that are closed early during testing.

Changes

File Changes
app.go - Added new error variable ErrTestGotEmptyResponse
- Modified Test method error handling to check for errTestConnClosed and fasthttp.ErrGetOnly
app_test.go - Updated error assertions to use require.ErrorIs()
- Added new test function Test_App_Test_drop_empty_response()
helpers.go - Added new error variable errTestConnClosed
- Replaced string literal error with named error variable in Write method
helpers_test.go - Updated error assertion in Test_Utils_TestConn_Closed_Write() to use require.ErrorIs()
ctx_test.go - Updated error assertions in Test_Ctx_Drop and Test_Ctx_DropWithMiddleware to use require.ErrorIs()

Assessment against linked issues

Objective Addressed Explanation
Fix app.Test() auto-failing when connection closes early [#3278]
Return "test: got empty response" for dropped connections
Improve testing for features like manual response flushing

Possibly related PRs

Suggested reviewers

  • gaby
  • sixcolors
  • efectn

Poem

🐰 A rabbit's tale of code so bright,
Where errors dance in testing's light,
Connections drop, but fear not, friend!
Our Fiber's strength will always mend,
With grace and care, we debug tonight! 🔧


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9efc3f0 and fd86be6.

📒 Files selected for processing (3)
  • app.go (3 hunks)
  • app_test.go (2 hunks)
  • ctx_test.go (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • app.go
🔇 Additional comments (5)
ctx_test.go (2)

Line range hint 5899-5930: LGTM! Well-structured test for Drop() functionality.

The test verifies that calling Drop() correctly returns ErrTestGotEmptyResponse and nil response. The test also includes a good control case with a regular handler.


5930-5930: LGTM! Good test coverage for Drop() with middleware.

The test ensures Drop() works correctly when called from a handler with middleware that modifies headers.

app_test.go (3)

1494-1494: LGTM! Improved error assertion.

Changed to use require.ErrorIs for more precise error type checking.


1510-1511: LGTM! Improved error assertion.

Changed to use require.ErrorIs for more precise error type checking.


1513-1525: LGTM! Good test coverage for Drop() empty response.

The test verifies that app.Test() correctly returns ErrTestGotEmptyResponse when a handler calls Drop().

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link

codecov bot commented Jan 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.15%. Comparing base (bc37f20) to head (fd86be6).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3279      +/-   ##
==========================================
+ Coverage   84.08%   84.15%   +0.06%     
==========================================
  Files         116      116              
  Lines       11541    11541              
==========================================
+ Hits         9704     9712       +8     
+ Misses       1406     1400       -6     
+ Partials      431      429       -2     
Flag Coverage Δ
unittests 84.15% <100.00%> (+0.06%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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)
app_test.go (1)

1513-1525: Test logic looks good, but needs formatting fixes.

The test case correctly verifies that c.Drop() returns ErrTestGotEmptyResponse. However, the code needs formatting fixes to meet Go standards.

Run the following commands to fix the formatting:

-func Test_App_Test_drop_empty_response(t *testing.T) {
-    t.Parallel()
-
-    app := New()
-    app.Get("/", func (c Ctx) error {
-        return c.Drop()
-    })
-
-    _, err := app.Test(httptest.NewRequest(MethodGet, "/", nil), TestConfig{
-        Timeout: 0,
-        FailOnTimeout: false,
-    })
-    require.ErrorIs(t, err, ErrTestGotEmptyResponse)
+func Test_App_Test_drop_empty_response(t *testing.T) {
+	t.Parallel()
+
+	app := New()
+	app.Get("/", func(c Ctx) error {
+		return c.Drop()
+	})
+
+	_, err := app.Test(httptest.NewRequest(MethodGet, "/", nil), TestConfig{
+		Timeout:       0,
+		FailOnTimeout: false,
+	})
+	require.ErrorIs(t, err, ErrTestGotEmptyResponse)
}
🧰 Tools
🪛 golangci-lint (1.62.2)

1514-1514: File is not gofumpt-ed with -extra

(gofumpt)


1514-1514: File is not goimports-ed

(goimports)

🪛 GitHub Actions: golangci-lint

[error] 1514-1514: File is not gofmt-ed with -s. Code formatting does not meet Go standards.


[error] 1514-1514: File is not gofumpt-ed with -extra. Code formatting does not meet enhanced Go standards.


[error] 1514-1514: File is not goimports-ed. Import formatting does not meet Go standards.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between bc37f20 and d2c3a90.

📒 Files selected for processing (4)
  • app.go (3 hunks)
  • app_test.go (2 hunks)
  • helpers.go (2 hunks)
  • helpers_test.go (1 hunks)
🧰 Additional context used
🪛 golangci-lint (1.62.2)
app_test.go

1514-1514: File is not gofumpt-ed with -extra

(gofumpt)


1514-1514: File is not goimports-ed

(goimports)

🪛 GitHub Actions: golangci-lint
app_test.go

[error] 1514-1514: File is not gofmt-ed with -s. Code formatting does not meet Go standards.


[error] 1514-1514: File is not gofumpt-ed with -extra. Code formatting does not meet enhanced Go standards.


[error] 1514-1514: File is not goimports-ed. Import formatting does not meet Go standards.

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: unit (1.23.x, macos-13)
  • GitHub Check: unit (1.23.x, windows-latest)
  • GitHub Check: Compare
  • GitHub Check: repeated
🔇 Additional comments (7)
helpers.go (2)

615-616: LGTM! Good error handling practice.

Defining errTestConnClosed as a package-level variable follows Go's best practices for error handling, enabling error comparison using errors.Is().


636-637: LGTM! Consistent error handling.

Using the predefined error variable instead of creating a new error improves consistency and enables proper error type checking.

helpers_test.go (1)

551-551: LGTM! Improved error type verification.

Using require.ErrorIs() instead of a generic error check ensures that the specific errTestConnClosed error is returned when writing to a closed connection.

app.go (2)

944-945: LGTM! Well-defined error variable.

The new error variable ErrTestGotEmptyResponse is appropriately defined at package level with a clear error message.


Line range hint 1027-1038: LGTM! Improved error handling for closed connections.

The changes correctly handle early connection closure:

  1. Ignores errTestConnClosed when combined with fasthttp.ErrGetOnly
  2. Returns ErrTestGotEmptyResponse for empty responses, which is expected when c.Drop() is called
app_test.go (2)

1494-1494: LGTM! Improved error assertion.

Using require.ErrorIs is more precise than comparing error strings.


1510-1511: LGTM! Consistent error handling.

The test now correctly checks for ErrTestGotEmptyResponse instead of a string comparison.

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)
app_test.go (1)

1517-1517: Fix formatting in function declaration

The function declaration has incorrect spacing. Let's fix it to match the codebase style.

-	app.Get("/", func (c Ctx) error {
+	app.Get("/", func(c Ctx) error {
🧰 Tools
🪛 golangci-lint (1.62.2)

1517-1517: File is not gofumpt-ed with -extra

(gofumpt)


1517-1517: File is not goimports-ed

(goimports)

🪛 GitHub Actions: golangci-lint

[warning] 1517-1517: File is not gofmt-ed with -s


[warning] 1517-1517: File is not gofumpt-ed with -extra


[warning] 1517-1517: File is not goimports-ed

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d2c3a90 and 9efc3f0.

📒 Files selected for processing (1)
  • app_test.go (2 hunks)
🧰 Additional context used
🪛 golangci-lint (1.62.2)
app_test.go

1517-1517: File is not gofumpt-ed with -extra

(gofumpt)


1517-1517: File is not goimports-ed

(goimports)


1522-1522: File is not gofumpt-ed with -extra

(gofumpt)

🪛 GitHub Actions: golangci-lint
app_test.go

[warning] 1517-1517: File is not gofmt-ed with -s


[warning] 1517-1517: File is not gofumpt-ed with -extra


[warning] 1517-1517: File is not goimports-ed


[warning] 1522-1522: File is not gofumpt-ed with -extra

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: unit (1.23.x, windows-latest)
  • GitHub Check: Compare
  • GitHub Check: repeated
🔇 Additional comments (3)
app_test.go (3)

1494-1494: Great improvement in error checking!

Using require.ErrorIs instead of require.Equal is more idiomatic and provides better error type checking.


1510-1511: Appropriate error type for empty response!

Using ErrTestGotEmptyResponse for timeout cases without failure flag is consistent with the PR's objective of improving error handling.


1513-1525: Well-structured test case that addresses the core issue!

This test case effectively verifies that app.Test() handles c.Drop() correctly by returning ErrTestGotEmptyResponse instead of failing.

🧰 Tools
🪛 golangci-lint (1.62.2)

1517-1517: File is not gofumpt-ed with -extra

(gofumpt)


1517-1517: File is not goimports-ed

(goimports)


1522-1522: File is not gofumpt-ed with -extra

(gofumpt)

🪛 GitHub Actions: golangci-lint

[warning] 1517-1517: File is not gofmt-ed with -s


[warning] 1517-1517: File is not gofumpt-ed with -extra


[warning] 1517-1517: File is not goimports-ed


[warning] 1522-1522: File is not gofumpt-ed with -extra

@grivera64 grivera64 force-pushed the bugfix(v3)/fix-autofail-app-test branch from 566cdb8 to 6456261 Compare January 12, 2025 02:03
@grivera64 grivera64 force-pushed the bugfix(v3)/fix-autofail-app-test branch from 6456261 to fd86be6 Compare January 12, 2025 02:05
@ReneWerner87 ReneWerner87 added this to the v3 milestone Jan 12, 2025
@ReneWerner87
Copy link
Member

@efectn @gaby can you also check

Copy link
Member

@gaby gaby left a comment

Choose a reason for hiding this comment

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

👍 LGTM

@ReneWerner87 ReneWerner87 merged commit 4e5fea1 into gofiber:main Jan 13, 2025
14 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jan 13, 2025
17 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

🐛 [Bug]: Fix app.Test() auto-failing when a connection is closed early
3 participants