Skip to content

Write unit tests #3

Description

@RandomHashTags

Unit testing is critical in code predictability, expected behavior and overall functionality, and should be a requirement for a networking library.

Separate unit tests per module.

Checklist:

General

  • Command line arguments
  • Custom hostname
  • Custom port
  • Different charsets
  • HTTPDateFormat
  • Routers
  • Router Groups
  • SIMD extensions (move to own repo?)

Routes

Unit tests for both static and dynamic routes.

  • Paths with parameters
  • Paths with wildcards
  • Case sensitive paths
  • Case insensitive paths
  • Compression
  • Different data representations
  • Redirects

Responders

Unit tests for both static and dynamic responders.

  • Conditional responder
  • Error responder

Middleware

Unit tests for both static and dynamic middleware.

  • CORS
  • Files
  • Metrics
  • Rate Limiting
  • Tracing

Cookies

  • Working with middleware
  • Working with routes and responders

Performance

  • Throughput
  • Latency
  • Stress test

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

compilation conditionsInvolves compilation conditions in some wayconvenienceRelates to convenient codecookiesRelates to HTTP CookiesembeddedRelates to Swift Embedded modeenhancementNew feature or requestperformanceRelates to performance behaviorsemver/patchSemantic Version PATCH changes (made backward compatible bug fixes)unit testsRelates to unit tests in some way

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions