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
#21 reminds me, that it would be nice, to get testname based on some metadata, not exactly on directory name.
for example:
deps file will be removed
metadata file will be added and will contain for example using syntax of https://docs.python.org/2/library/configparser.html
[Description]
name = superpingtest
summary: this test is testing ping somehow
and it is very perfect ultimate test
[Dependencies]
rpm=abc def
deb=abc xyz
[Executables]
server=../othertest/server
client=client
[Environment]
variable=I dont know what to write there now
Then it will be possible easily extend schedule possibilities or add some filtering options (some tests are irrelevant for some environments for example)
and also names will be independent on directory structure.
more less all of sections could be omitted, only description have to be there.
The text was updated successfully, but these errors were encountered:
Or there can be used json parser for config file instead of that one, becasue it is now used, so no more python dependencies needed, although congfigparser is general part of python.
#21 reminds me, that it would be nice, to get testname based on some metadata, not exactly on directory name.
for example:
deps file will be removed
metadata file will be added and will contain for example using syntax of https://docs.python.org/2/library/configparser.html
Then it will be possible easily extend schedule possibilities or add some filtering options (some tests are irrelevant for some environments for example)
and also names will be independent on directory structure.
more less all of sections could be omitted, only description have to be there.
The text was updated successfully, but these errors were encountered: