Skip to content

Expand testing to include more interesting fields #658

@BenHenning

Description

@BenHenning

Check for duplicates

  • I have searched for similar issues before opening a new one.

Problem

#563 and RaspberryPiFoundation/blockly#9221 both explain a variety of failure modes for field editors and focus. Attempts to fix the former have caused the latter, largely due to insufficient manual and automated testing.

Request

We need tests to demonstrate these scenarios that fixes can be trusted. One approach for determining these:

  • Collect all failure classes discovered with and without the fixes as part of MakeCode's testing.
  • Map these failure modes back to specific fields that MakeCode uses.
  • Map these fields back to sufficiently similar fields in Blockly samples, or create new fields.
  • Update the test playground(s) for this plugin to reference the fields.
  • Add new test cases that trigger both sets of failures in their entirety (far beyond what chore: Add new tests for ephemeral focus #649 is doing).
  • Leverage these tests to establish proper long-term fixes for field and focus issues.

Alternatives considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions