Skip to content

[Guidance/Documentation] Message Bus Artifacts #3261

Open
@thomhurst

Description

@thomhurst

In the new testing platform, when using the message bus, apart from the main use of publishing test node updates, there's also a few other things we can publish out of the box, mainly being artifact objects.

image

I can't see any documentation on these so just wondered:

  • What the idea/use case/general direction for usage for these would be?
  • If I pushed an artifact to the message bus, what would (and how would it) appear and where? Would an IDE show me a file? Would the dotnet cli give me a path to some outputs?
  • What do you see as a Session artifact? Maybe like an overall report or something? And what would you consider as a test node artifact? Maybe a UI test that took screenshots or videos? Again, if this was the case, how would these be reported/displayed back to the user?

So overall this issue is for better documentation around artifacts and how you envision any framework creators using them.

Activity

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

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions