The settings for scanning a feature that performs duplicate data checking
Item to be used
|"Substitute list parameter"|
The following article describes the setting items available in each template..
[Related article]"The purpose of Pre processor"
■Ex. of unsuccessful scenarios
In case of a registration feature that prevents the same e-mail address from being signed up more than once.
When scanning features that perform duplicate checking on data to be registered, as seen in a member registration feature, data that has already been registered will be blocked and an error will occur since a proxy log value recorded in Vex is sent as it is.
To avoid this, you should set up "Substitute list parameter" so that a different value is to be sent for each request.
Set up Substitute list parameter
1. Identify a parameter that is required to be handed over
When a scenario of ID:28 (input) -> ID:29 (confirmation) -> ID:31 (completion) is created and Test Access is performed, an error will occur because values used during logging are sent as they are.
At this time, you can identify duplicate-checked parameters from HTML display and request parameter information.
<Example: Confirm the Test results >※The red frame is the confirmation tool that is mainly used.
<HTML display of ID:29 (confirmation) >
<Confirm the request parameter information>
2. Set up Pre processor
Set up "Substitute list parameter" for the ID:29 Pre processor so that different "mail_address" will be sent for each request.
See the following article for details on how to set up Handler setting items.
[Related article]"Handler setting items"
3. Run Test Access to check if the page transition is successful
Check if the scenario you have created can reproduce the page transition. For how to check, see the following article.
[Related FAQ]"How to verify the effectiveness of scenarios"