141 lines
6.8 KiB
Plaintext
141 lines
6.8 KiB
Plaintext
# Instruction
|
||
- You are an expert in cleaning process data descriptions. Given a task, you are provided with a set of annotation description
|
||
data for a certain visual LLM related to human user operation videos. Plus, You are provided with full trace of playwright action,
|
||
whic includes action and url before and after the action.
|
||
- You need to analyze all the descriptive data and ultimately summarize a complete and reasonable user operation description that can accomplish the given task.
|
||
- For each strategy, give a clear list of the low level action sequence.
|
||
|
||
# Task
|
||
What is the date when I made my first purchase on this site?
|
||
|
||
# Annotation description
|
||
### Step-by-Step Actions in the Video Segment
|
||
|
||
#### 1. **Action:** I click on the "My Orders" link in the left sidebar menu.
|
||
- **Page Changes:** The page transitions to display a list of orders under the "My Orders" section. This list includes columns for Order #, Date, Order Total, Status, and Action.
|
||
- **Possible Purpose:** The likely intent is to view past order details, possibly to check the status of an order, review items purchased, or consider reordering products.
|
||
|
||
#### 2. **Action:** I hover over an order entry in the list (specifically Order # 000000182).
|
||
- **Page Changes:** No significant change occurs on the page, but the order entry appears highlighted, indicating it is selected or focused.
|
||
- **Possible Purpose:** The purpose is likely to prepare for further interaction with this specific order, such as viewing its details or initiating a reorder.
|
||
|
||
#### 3. **Action:** I click on the "View Order" link associated with Order # 000000182.
|
||
- **Page Changes:** The page navigates to a detailed view of Order # 000000182. This new page provides comprehensive information about the order, including the items ordered, their quantities, prices, and any additional order-specific details like shipping and billing information.
|
||
- **Possible Purpose:** The intent is to review the specifics of this particular order, which may include verifying the items purchased, checking the order total, or retrieving shipping details.
|
||
|
||
#### 4. **Action:** I scroll down on the detailed order page.
|
||
- **Page Changes:** The visible content on the page shifts downward, revealing more details about the order, such as item descriptions, pricing breakdowns, and possibly customer notes or order comments.
|
||
- **Possible Purpose:** The purpose of scrolling is to access and review additional information that was not initially visible, ensuring a thorough understanding of the order details.
|
||
|
||
#### 5. **Action:** I click on the browser's back button to return to the "My Orders" list page.
|
||
- **Page Changes:** The page returns to the "My Orders" section, displaying the list of orders as it was before navigating to the detailed order view.
|
||
- **Possible Purpose:** The intent is to go back to the overview of all orders, potentially to select and view another order or to complete reviewing the current order details.
|
||
|
||
### Summary
|
||
In this video segment, I navigate through the "My Orders" section of the website to view the details of a specific order (Order # 000000182). My actions include selecting the "My Orders" menu, focusing on a particular order, accessing its detailed view, reviewing the information, and then returning to the main orders list. Each step is performed methodically to obtain and verify specific order-related information.
|
||
|
||
# Playwright action
|
||
[
|
||
{
|
||
"action_uid": "link_My Orders",
|
||
"idx": 0,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"My Orders\")",
|
||
"before": {
|
||
"url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/customer/account/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/customer/account/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "link_Page 4",
|
||
"idx": 1,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"Page 4\")",
|
||
"before": {
|
||
"url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/sales/order/history/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-135-39-80.us-east-2.compute.amazonaws.com:7770/sales/order/history/"
|
||
}
|
||
}
|
||
]
|
||
|
||
# Output format
|
||
- 先总结整个任务的Objective，然后按照Strategy-SubStrategy-action三级层次来给出整个过程，
|
||
- 接着给出整个操作流程后的观察和有趣的发现，最后严格按照json格式输出三级层次的过程描述。
|
||
- 最后的输出json应该是包在```{json}```之间，最底层动作需要包含描述、对应的playwright动作指令顺序编号，以及具体指令内容。
|
||
|
||
# Example
|
||
### Complete User Operation Description to Display Labeled Issues in kkroening/ffmpeg-python
|
||
|
||
**Objective:** Filter and display all issues labeled as "question" in the kkroening/ffmpeg-python repository.
|
||
|
||
---
|
||
|
||
#### **Strategy 1: Navigate to the Repository**
|
||
**Low-Level Action Sequence:**
|
||
1. **Search for the user "kkroening"**
|
||
- Click the global search bar (placeholder: "Search GitLab").
|
||
- Type "kkroening" and press `Enter`.
|
||
2. **Select the user from results**
|
||
- Click the "Users" tab in search results.
|
||
- Click on "Karl Kroening @kkroening" in the user list.
|
||
3. **Access the repository**
|
||
- Navigate to the "Personal projects" section.
|
||
- Click on the "ffmpeg-python" project.
|
||
|
||
---
|
||
|
||
#### **Strategy 2: Filter Issues by Label**
|
||
**Low-Level Action Sequence:**
|
||
1. **Open the Issues tab**
|
||
- Scroll to the left sidebar menu.
|
||
- Click the "Issues" tab (displaying the count, e.g., "Issues 402").
|
||
2. **Apply label filtering**
|
||
- Click the search/filter bar in the issues list.
|
||
- Select the "Label" dropdown from the filter options.
|
||
- Type or select "question" from the label dropdown.
|
||
- Click the search/apply button to confirm the filter.
|
||
|
||
---
|
||
|
||
#### **Final Oberservation**
|
||
The issues list will refresh to show only issues with the "question" label. The URL will reflect the filter:
|
||
`.../ffmpeg-python/-/issues/?label_name[]=question`.
|
||
|
||
---
|
||
|
||
### Key Observations from Playwright Trace
|
||
- The final URL after filtering:
|
||
`http://ec2-3-135-39-80.../ffmpeg-python/-/issues/?label_name%5B%5D=question`
|
||
confirms the "question" label filter is applied.
|
||
- Critical interactions include selecting the "Label" dropdown and explicitly choosing "question" to refine results.
|
||
|
||
### Final output
|
||
```json
|
||
[{
|
||
"strategy" : "Navigate to the Repository",
|
||
"substrategies": [
|
||
{
|
||
"substrategy": "Search for the user \"kkroening\"",
|
||
"actions" : [
|
||
{
|
||
"description": "Click the global search bar (placeholder: \"Search GitLab\"). ",
|
||
"playwright_idx" : 18,
|
||
"playwright_instruction" : "frame.pressget_by_placeholder(\"Search GitLab\")Enter"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"substrategy": "Select the user from results",
|
||
"actions" : [
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"strategy" : "Filter Issues by Label",
|
||
"substrategies" : [
|
||
]
|
||
}]
|
||
``` |