Skip to content

x/playground: simplify development and testingย #69403

Open
@findleyr

Description

@findleyr

The playground development setup requires Docker, and as a result there is relatively little test coverage using go test (and therefore very little coverage in our default CI). CL 612456 is an example of a small change where a test would have been nice, but was not feasible due to friction and time constraints. Proof: in https://go.dev/cl/549015, I had actually started this fix for a related issue, and stalled because it was a low priority and I felt a test was warranted.

As a de-facto-but-superficial maintainer of the playground, I think this friction is holding back playground fixes and other improvements. From first principles, we should be able run the playground without Docker, and in doing so should be able to write end-to-end tests.

I think this is a good candidate for a friction fixit week.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrictionNuisances that make good candidates for our "friction" fix-it weeksNeedsInvestigationSomeone must examine and confirm this is a valid issue and not a duplicate of an existing one.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions