@TruninDenis I did not report it. They will ask if this issue affects Go-Live and stuff like that, and after I will have answered all the questions, they will give it priority 3 and archive the case, and then I will be asked to provide feedback on how good they were at archiving the case.
@PalleAgermark 5 words in the product name were not enough. 30 words would result in word wrapping -> extra line above the URL entry field -> profit
@PalleAgermark I have mixed feelings about all those limitations by default. So far “internal” and “private” keywords were pain in the butt on real customer projects. Looking forward to see “[Hookable(false), Wrappable(false)] internal private SalesTable find(…)” one day
@PalleAgermark OK, so now one can write a script, that will open a dialog with a field for a T-SQL statement, run the statement, then set its own status back and be ready for a new T-SQL. Sound flexible enough.
@FrankHuether Thanks, all in all it looks like there is no way to exclude a test with an attribute. Instead, every other test class must be decorated with some attribute, which may be used as a filter then.