Testing Architecture Review

Goals

• Review architecture of testing support in extension
• If we have major changes, then review overall architecture of the extension.

Data Models

• Can be simplified by making the structure flat
• Each item will have a unique identifier (id)
• Proposed structure
  • Discovery - use what we have today
  • Test results (will be streamed back - events/response style)

// Add the following to each test
// This information will not be available on the file, suite level, etc..
result: {
	status: <enum status>,
	error: {line, reason, stack, ....}
	time: milliseconds
},

Adapter = Event<test, result> Model = Event<test, result>

ViewModel handle event - Model

Tree

Adapter for discovery, running & debugging

• Use of python code instead of scraping stdout.
  • Python code to build, parse CLI args.
• Support streaming output (via stdout, socket, etc) through an abstraction.
  • With support to send data and logging into the same stream
  • I.e. message based protocol

General notes

• Improved testability