feat: improved query syntax

[Xiaoy312]

GitHub Issue (If applicable): #89

PR Type

What kind of change does this PR introduce?

• Feature

What is the new behavior?

new improved query syntax:

• search terms are separated by space

  c# identifier is quite limited, space is definitely not a valid character, so is minus-sign
  multiple consecutive spaces are treated same as one

• search terms are case insensitive
• all search terms are chained with AND logic
• - can be used before any term for exclusion, effectively filtering them out
• tags can be used to match certain part of the test: // syntax: tag:match_text

  tag are case insensitive

  • class or c matches the class name
  • method or m matches the method name
  • display_name or d matches the display name in [DataRow] or [DynamicData]
  • full_name or f matches the full name of method
  • params or p matches the parameters of [DataRow] or [DynamicData](unrolled)
  • at or @ (without colon) matches the [DataRow] or [DynamicData] case at specific index (DynamicData: index within the source)
• within a tag, , can be used to specify multiple potential matches (chained by OR logic)

  eg: @0,1,2 or at:0,1,2 // matches 0st, 1nd, 2rd [DataRow] or entry within [DynamicData]

• match text can be double-quoted to contain spaces, and use \" to escape double-quote within a double-quoted match text:

  eg: p:"1,\"args 2\",3"

• use ^ and $ to perform head or tail match, or both to perform full match

  eg: c:^List m:Changed$ d:^exactly_this_text$

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Other information

Currently we can match multiple tests (by OR logics) via ; delimiter. This is no longer supported in the new syntax.

[Xiaoy312]

todo:

• add an entry in the doc
• fix: tag-less term logics
• ~~``allow ; within trimmed term text to act like old impl
  ^ changed to `,`

[agneszitte]

Suggested change

	## Test runner (UnitTestsControl) filtering syntax
	- Search terms are separated by space. Multiple consecutive spaces are treated same as one.
	- Multiple search terms are chained with AND logic.
	- Search terms are case insensitive.
	- `-` can be used before any term for exclusion, effectively inverting the results.
	- Special tags can be used to match certain part of the test: // syntax: tag:term
	- `class` or `c` matches the class name
	- `method` or `m` matches the method name
	- `displayname` or `d` matches the display name in [DataRow]
	- Search term without a prefixing tag will match either of method name or class name.
	## Test runner (UnitTestsControl) filtering syntax
	- Search terms are separated by space. Multiple consecutive spaces are treated the same as one.
	- Multiple search terms are chained with AND logic.
	- Search terms are case insensitive.
	- `-` can be used before any term for exclusion, effectively inverting the results.
	- Special tags can be used to match certain parts of the test: // syntax: tag:term
	- `class` or `c` matches the class name
	- `method` or `m` matches the method name
	- `displayname` or `d` matches the display name in [DataRow]
	- Search term without a prefixing tag will match either method name or class name.

[agneszitte]

Suggested change

	/// Like <see cref="string.Split(char[])"/>, but allows exception to be made with a Regex pattern.
	/// Like <see cref="string.Split(char[])"/>, but allows exceptions to be made with a Regex pattern.

[agneszitte]

Suggested change

	/// <param name="ignoredPattern">segments matched by the regex will not be splited.</param>
	/// <param name="ignoredPattern">segments matched by the regex will not be split.</param>

[agneszitte]

Suggested change

	// fixme: DisplayName will also matches parameters
	// fixme: DisplayName will also match the parameters

[agneszitte]

fixme: ?

[agneszitte]

Suggested change

	/// <returns>If all 'tag' filters matches the value, or true if the none filters are of 'tag'.</returns>
	/// <returns>If all 'tag' filters match the value, or true if the none filters are of 'tag'.</returns>