Skip to content

Revise testing emulators to the subclass and multioutput #578

Open
@sgreenbury

Description

@sgreenbury

Might be worth drawing up an updated inheritance tree diagram for our Emulators, and also thinking about what level(s) we should be applying testing. I guess here you are doing the basic output type assertions in the classes themselves but would we want separate tests for each of these? - at the moment in test_experimental_base.py we just have TestPyTorchBackend

Originally posted by @edwardchalstrey1 in #561 (comment)

To reduce repetition across tests to each emulator, revise tests to be per subclass (add following #542)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    📋 Product backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions