You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
P0: Manager is evaluated before the command runs, while the Comparator in Output is evaluated after - this is confusing and prevents legit scenarios. Manager should only be evaluated after the command has run.
P0: remove dependency on *testing.T and replace by tig.T everywhere
P1: following the rewrite of Command, test.Command is now a (mostly) empty shell - cleanup / refactor
P1: reintroduce Env, WD, etc to the command debug output
P1: add Config/Data details to the debug output
P1: API breaking: change comparators signature (remove info + tig.T)
P1: currently, the command is executing inside data.TempDir(), so, there is no distinction between . and TempDir from the command perspective. We may want to address that.
P1: missing something like .AddCleanup() when a routine inside Setup does want to add additional cleaning
P1: requirements should be able to manipulate the environment
P2: use of data.Identifier in subtests hoping to get the parent testid may be error prone - rethink Identifier()?
The text was updated successfully, but these errors were encountered:
apostasie
changed the title
Issues and requirements for next test-tooling updates
[Tigron]: roadmap and tracking epic for work on test tooling
Apr 5, 2025
PR
Pending review
Work in progress
Test suites to rewrite
Issues and features
Manager
is evaluated before the command runs, while theComparator
in Output is evaluated after - this is confusing and prevents legit scenarios. Manager should only be evaluated after the command has run.Data
- need something to manipulate temp files ([STACKED] [WIP] [Tigron]: revised Data interface #4081)info
+tig.T
).
andTempDir
from the command perspective. We may want to address that..AddCleanup()
when a routine insideSetup
does want to add additional cleaningThe text was updated successfully, but these errors were encountered: