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
In order to eventually phase out runtest files the test variants (i.e. the different test parameters) have to be moved from rutnest files somewhere, I guest the most logical plan would be to move them into the tst_test structure.
Apart from having all the information in a single place that would mean:
the test variants would be exported into metadata and could be used by the test runner
the test can list all test variants (e.g. with -t parameter)
specific test variant could be executed by a shortcut (e.g. -t 2)
The open question is how to encode these. Easiest solution would be strings with a list of command line parameters, something as:
In order to eventually phase out runtest files the test variants (i.e. the different test parameters) have to be moved from rutnest files somewhere, I guest the most logical plan would be to move them into the tst_test structure.
Apart from having all the information in a single place that would mean:
-t
parameter)-t 2
)The open question is how to encode these. Easiest solution would be strings with a list of command line parameters, something as:
The corresponding kirk issue: linux-test-project/kirk#13
The text was updated successfully, but these errors were encountered: