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
There are a lot of cool tests here, but there are still some tests that does not fit in with our policies. Because of this we want to filter out some tests (not just one or two).
To get a good overview of all tests, what they do, the URL to specifics, their specific TAG etc, I tried to run through all test-files and fetch this information. However, I ended up running into problems since a lot of tests have been written a bit differently. What I preferably would like to end up with is an easily fetchable table with all tests publicly available, with each tests specific information and TAG. Kind of like this:
With this I can specify internal categories/groups to each test so that I have control over which tests we would like to run based on which level of security a customer is/want to be at. This way we avoid excessive failed tests which would just give false negatives.
Below are examples of how the tests have been written differently, which makes it harder to gather the necessary information.
This is an example of a test that is formatted in a good way:
Here I can easily fetch the name of each test, its specific TAG as well as the URL to more information.
This is an example of a test that is decently formatted:
Here I can at least get the name and the TAG without too much hassle.
Then there is these types:
Where even the correct TAG isn't easy to fetch programatically.
Could for example the -Tag parameter be mandatory for every test (every line in a .tests.ps1 file that starts with 'It') so that every test has an easily noticable tag? And preferably a -Url parameter as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There are a lot of cool tests here, but there are still some tests that does not fit in with our policies. Because of this we want to filter out some tests (not just one or two).
To get a good overview of all tests, what they do, the URL to specifics, their specific TAG etc, I tried to run through all test-files and fetch this information. However, I ended up running into problems since a lot of tests have been written a bit differently. What I preferably would like to end up with is an easily fetchable table with all tests publicly available, with each tests specific information and TAG. Kind of like this:
With this I can specify internal categories/groups to each test so that I have control over which tests we would like to run based on which level of security a customer is/want to be at. This way we avoid excessive failed tests which would just give false negatives.
Below are examples of how the tests have been written differently, which makes it harder to gather the necessary information.
This is an example of a test that is formatted in a good way:
Here I can easily fetch the name of each test, its specific TAG as well as the URL to more information.
This is an example of a test that is decently formatted:
Here I can at least get the name and the TAG without too much hassle.
Then there is these types:
Where even the correct TAG isn't easy to fetch programatically.
Could for example the -Tag parameter be mandatory for every test (every line in a .tests.ps1 file that starts with 'It') so that every test has an easily noticable tag? And preferably a -Url parameter as well.
Beta Was this translation helpful? Give feedback.
All reactions