How to scan data deletion feature

The following articles describe the setting items available in each template.
[Related article]"The purpose of Pre processor"
[Related article]"The purpose of Post processor"

■Example of Error scenario


■Setting overview
To scan a data deletion feature, you need to create a scenario in which enough data is registered to be deleted because the registered data will be actually deleted each time Test access and request is sent.

In addition, when IDs are assigned to data, they must be properly handed over.

In this case, you can perform a scan successfully by arranging the data to be deleted before moving to the page that processes deletion.

There are two main methods to do this.

■Setting methods in detail
【Common step】Identify the parameter that must be handed over


In the above scenario in the order of  ID:117(List)->ID:119(Detail)->ID:121(Deletion), you can see that the data to be deleted is specified by "article_Id" in ID:119 (Detail), and by "deleteTarget " in ID :121 (Delete).

-The request parameter of ID:119


The request parameter of ID:121



[Method 1] Arrange enough data to be deleted in advance
You can avoid errors by specifying a sufficient amount of data to be used for scanning in advance.

(1)Arrange data to be used for scanning
As a guideline, the number of parameters to be arranged must be about 50 times the number of parameters to be scanned.
Check the "Number of parameters" column in the Proxy Log List to see how many parameters are specified.

(2)Set up handover of the value
Set up handover of "article_Id" in Pre processor of ID:117(List)->ID:119(Detail), and set up handover of "deleteTarget"in Pre processor of ID:119(Detail)->ID:121(Delete).
*The setting item to be applied varies depending on the specification of the target.

As an example, how to set up handover of  "deleteTarget" is described here.
As shown below,  the duplicate hidden parameter with the request parameter has the same value. In this case,  you can apply "Hand over parameter (Specify only name)".

-The response parameter of ID:119

Similarly, in case of "article_Id", identify the handover source to set up handover.
(Detail is omitted here).

See the following articles for how to identify values and how to set up Handler in detail.
[Related article]"Handler setting guide"
[Related article] "Handler setting items"


(3)Perform Test access to see if the page transition is properly performed
Verify that the scenario you have created can reproduce the page transition diagram properly by referring the following article.

[Related article] "How to verify the effectiveness of scenarios"


[Method 2] Create a scenario that performs data registration
You can avoid an error caused by a lack of data by setting up Pre processor to add data before data is deleted during scanning.
In this example, it is set up in Pre processor.

(1)Create a scenario using Pre processor
Set up Pre processor for the target message ID to configure the transitions before the page where the deletion is performed.
Set up Pre processor to make the scenario proceed as below.
Login (if necessary) -> Registration process (*) ->List page(ID:117) )->Detail page (ID:119)->Delete(ID:121)
You must register all transitions required for data registration.

See Quick Start "4.2.2.3.2. <STEP2> Editing Handler" or the following articles for Handler setting method.
[Related article] "Handler setting guide"
[Related article] "Handler setting items"

(2)Set up handover of the value
Set up handover of "article_Id" in Pre processor of ID:117(List)->ID:119(Detail) and, set up handover of "deleteTarget" in Pre processor of ID:119(Detail)->ID:121(Deletion process).
For more detail, see [Method 1](2).

(3)Perform Test access to see if the page transition is properly performed
Verify that the scenario you have created can reproduce the page transition properly by referring to the following article.

[Related article] "How to verify the effectiveness of scenarios"

*The scenario that performs data registration can be configured in Post processor as well.