Skip to content
This repository was archived by the owner on Jul 6, 2018. It is now read-only.
This repository was archived by the owner on Jul 6, 2018. It is now read-only.

Test List #42

Description

@italoacasas

cc: @jasnell, @mcollina, @addaleax

I start working on the test list today, I will be updating the list while gathering more information. I'm open the issue that way everyone can give feedback about what should be in/out/priority, etc...

Test List

  • Errors conditions (James list)
  • Server with connections that prematurely exists (James list)
  • Basic server with configuration options set (James list)
  • Server that responds with a file (pipe test) (James list)
  • Basic server with simple async response (James list)
  • Basic server with and without TLS. Create server instance, start listening, accept request with simple sync response (James list)
  • Server client error
  • Response Status code
  • HTTP Methods
  • Invalid (URLs and headers fields)
  • uncaughtException
  • Default values (port, encoding, method, headers)
  • Connect (request, response, length)
  • DNS error

Client

  • abort event
  • abort
  • aborted event
  • agent
  • check HTTP token
  • default headers exist
  • default
  • encoding
  • get URL
  • keep alive release before the finish
  • parse error
  • pipe end
  • read in error
  • readable
  • reject chunked with content length
  • response domain

Activity

  1. mcollina commented on Mar 4, 2017

    @mcollina
    SponsorMember

    hey @italoacasas, since today we have a minimal http2 client (see #43). The API is definitely not finalized, but we can definitely get some help in ramping up the test and test coverage. Maybe we can turn that bullet list into a task lists, and start adding those.
    I think those tests would help in driving the client API.

    cc @jasnell

  2. italoacasas commented on Mar 6, 2017

    @italoacasas
    Author

    @mcollina I'm not going to be around next week.

    • I change the list for bullets point.

    • The list is a work in progress, still pending most of the server tests. But at least we have a guide for a portion of what we need to do. I will work on this if no-one does when I come back.

    • Maybe creating a Project is a good idea, remember the way we did this for the streams internal states tests?

  3. mcollina commented on Mar 6, 2017

    @mcollina
    SponsorMember

    @italoacasas definitely. We can do a project, and open some issues here.
    It's a ton of work, as I expect those features not to work as expected (vs what we did for streams).

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions