After verifying the planning of the use cases added to a certain amount, they can already use cases regression, time-saving use case execution, and can find some potential bug.
Recently we met matching a space with a table in the preparation of the return script, to matching content simplified as follows:
wherein: qbv_base_test cfg = pkt_len_64B and connected with a space, qbv_base_test cfg = pkt_len_65B connection with Table.
before adding copy all use cases, which are connected by a space.
- Add a space pattern matching
the position indicated by the arrow a space above figure, with the result of this pattern matching is
| Space | Pass |
| Table | Fail | - Pattern matching with \ S *
| Space | Pass |
| the Table | Pass | - Pattern matching with \ t
| Space | Fail |
| the Table | Pass |
Summary: From the above comparison can be seen when the matching table, by \ t or \ s are possible matching; with "\ s " (which has a space), the individual not match the original table is also appreciated by spaces. composed, split into space + \ s * can match, but the reality could not match. solving it you
