201 lines
9.1 KiB
Plaintext
201 lines
9.1 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
|
||
Tell me the reasons why customers like Circe's products
|
||
|
||
# Annotation description
|
||
### Step-by-Step Actions in the Video Segment
|
||
|
||
#### 1. **Opening the Reports Menu**
|
||
- **Action:** I click on the "Reports" menu item in the left sidebar.
|
||
- **Page Changes:** The page transitions to display a dropdown menu with various report categories such as "Marketing," "Sales," "Orders," "Customers," etc.
|
||
- **Possible Purpose:** The likely intent is to navigate to a specific report section for detailed analysis or management.
|
||
|
||
#### 2. **Selecting the "Reviews" Section**
|
||
- **Action:** I hover over the "Reviews" option within the "Reports" dropdown menu.
|
||
- **Page Changes:** The "Reviews" submenu appears, showing options like "By Customers" and "By Products."
|
||
- **Possible Purpose:** The intention is to access review-related data, possibly to analyze customer feedback or product ratings.
|
||
|
||
#### 3. **Choosing "By Products" Report**
|
||
- **Action:** I click on the "By Products" option under the "Reviews" submenu.
|
||
- **Page Changes:** The page loads the "Product Reviews Report," displaying a table with columns for ID, Product, Reviews, Average, Average (Approved), Last Review, and Action.
|
||
- **Possible Purpose:** The goal is to view and manage product reviews, perhaps to monitor product performance based on customer feedback.
|
||
|
||
#### 4. **Navigating the Product Reviews Report**
|
||
- **Action:** I scroll through the "Product Reviews Report" table.
|
||
- **Page Changes:** The table content scrolls, revealing more products and their respective review details.
|
||
- **Possible Purpose:** The aim is to review a comprehensive list of product reviews to identify trends, issues, or high-performing products.
|
||
|
||
#### 5. **Clicking on "Show Reviews" for a Specific Product**
|
||
- **Action:** I click on the "Show Reviews" link next to a specific product in the "Action" column.
|
||
- **Page Changes:** A new page titled "Reviews" opens, listing individual reviews for the selected product, including details like ID, Created date, Status, Title, Nickname, Review text, and actions like "Edit" or "Delete Review."
|
||
- **Possible Purpose:** The intention is to delve into the specific reviews for that product, possibly to moderate, edit, or analyze the feedback in detail.
|
||
|
||
#### 6. **Editing a Review**
|
||
- **Action:** I click on the "Edit" link next to a specific review in the "Reviews" list.
|
||
- **Page Changes:** The page transitions to an "Edit Review" form, where I can modify details such as Status, Nickname, Summary of Review, Review text, Detailed Rating, and Summary Rating.
|
||
- **Possible Purpose:** The goal is to update or correct the review information, perhaps to address inaccuracies, improve clarity, or manage content quality.
|
||
|
||
#### 7. **Saving the Edited Review**
|
||
- **Action:** After making changes in the "Edit Review" form, I click the "Save Review" button.
|
||
- **Page Changes:** The page reloads, confirming the review has been updated, and I am redirected back to the "Reviews" list for the product.
|
||
- **Possible Purpose:** The intent is to finalize and apply the edits made to the review, ensuring the updated information is saved and reflected in the system.
|
||
|
||
---
|
||
|
||
This sequence of actions strictly follows the observable interactions within the provided video segment, focusing solely on the described steps without incorporating external context or assumptions.
|
||
|
||
# Playwright action
|
||
[
|
||
{
|
||
"action_uid": "link_\ue60a Reports",
|
||
"idx": 0,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"\ue60a Reports\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/admin/dashboard/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/admin/dashboard/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "link_By Products",
|
||
"idx": 1,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"By Products\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/admin/dashboard/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/admin/dashboard/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "action_2",
|
||
"idx": 2,
|
||
"action_repr": "frame.clicklocator(\"#gridProducts_filter_name\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/reports/report_review/product/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/reports/report_review/product/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "action_3",
|
||
"idx": 3,
|
||
"action_repr": "frame.presslocator(\"#gridProducts_filter_name\")Enter",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/reports/report_review/product/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/reports/report_review/product/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "link_Show Reviews",
|
||
"idx": 4,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"Show Reviews\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/reports/report_review/product/filter/bmFtZT1jaXJjZSZjcmVhdGVkX2F0JTVCbG9jYWxlJTVEPWVuX1VT/form_key/ryRSnhD1Wzkxi8pd/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/reports/report_review/product/filter/bmFtZT1jaXJjZSZjcmVhdGVkX2F0JTVCbG9jYWxlJTVEPWVuX1VT/form_key/ryRSnhD1Wzkxi8pd/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "cell_I recently purchased the Circe Hooded Ice Fleec...",
|
||
"idx": 5,
|
||
"action_repr": "frame.clickget_by_role(\"cell\", name=\"I recently purchased the Circe Hooded Ice Fleec...\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/index/productId/1210/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/index/productId/1210/"
|
||
}
|
||
}
|
||
]
|
||
|
||
# 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" : [
|
||
]
|
||
}]
|
||
``` |