Ginkgo fails if some focused test is left in the codebase (FIt, FEntry, etc), avoiding the risk of committing code with focused tests in code that may let us think the CI is good while it's running a subset of tests.
Is your feature request related to a problem? Please describe.
This is the logic currently implemented in the main branch:
If headers criteria are configured, a request is filtered in if it matches both headers and urls. If headers criteria are NOT configured, the probability options are used.
Some applications are not case-sensitive on the URL parameters, and may look for arguments presented under any fantasist format. One could argue that we could turn the complete string to lower case before performing the lookup, but that would also change the values, which is not desired. A better approach would be to improve url_param, urlp, and urlp_val() to take a
A clear and concise description of the bug.
when my asp.net core 3.1 app host in IIS, the url console is 127.0.0.1，so，when i have Multiple instances，the instances name will be the same,such as 127.0.0.1:svaname:port，eureka server think they are a single instance.
i print the console in source code：
): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
at [Source: (byte[])"
<!DOCTYPE html PUBLIC "-//W
Ginkgo fails if some focused test is left in the codebase (FIt, FEntry, etc), avoiding the risk of committing code with focused tests in code that may let us think the CI is good while it's running a subset of tests.