308 lines
15 KiB
Plaintext
308 lines
15 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
|
||
Approve the positive reviews to display in our store.
|
||
|
||
# Annotation description
|
||
## Part 1
|
||
### Step-by-Step Actions in the Video Segment
|
||
|
||
#### 1. **Action:** I click on the "Customers" menu item in the left sidebar.
|
||
- **Page Changes:** The page transitions from the "Dashboard" to the "Customers" section, displaying a list of customers and related options such as "All Customers," "Customer Logs," "Groups," etc.
|
||
- **Possible Purpose:** The likely intent is to navigate to the customer management area to view or manage customer data.
|
||
|
||
#### 2. **Action:** I hover over the "Marketing" menu item in the left sidebar.
|
||
- **Page Changes:** A dropdown menu appears under the "Marketing" section, revealing options like "Communications," "Newsletter Templates," "Newsletter Queue," "Newsletter Subscribers," and "Pending Reviews."
|
||
- **Possible Purpose:** The intention is to explore the marketing tools available, possibly to access a specific feature related to marketing activities.
|
||
|
||
#### 3. **Action:** I click on the "Pending Reviews" option within the "Marketing" dropdown menu.
|
||
- **Page Changes:** The page navigates to the "Pending Reviews" section, showing a table with columns for ID, Created date, Title, Nickname, Review, Status, Product, Store View, Type, SKU, and Action.
|
||
- **Possible Purpose:** The goal is to review and manage pending product reviews, which might require approval or further action.
|
||
|
||
#### 4. **Action:** I click on a specific review entry in the "Pending Reviews" table.
|
||
- **Page Changes:** The page transitions to the "Edit Review" page for the selected review. This page includes detailed information about the review, such as the summary rating, detailed rating, status, nickname, title, review text, product details, and options to delete, reset, or save the review.
|
||
- **Possible Purpose:** The purpose is to edit or approve the specific pending review, ensuring it meets the necessary criteria before publication.
|
||
|
||
#### 5. **Action:** I click the "Save Review" button at the top right corner of the "Edit Review" page.
|
||
- **Page Changes:** The page likely confirms the action taken (though the exact confirmation is not shown in the segment), and the review status may update accordingly.
|
||
- **Possible Purpose:** The intent is to save any changes made to the review, effectively processing it for approval or modification.
|
||
|
||
### Summary
|
||
In this video segment, I navigate through the website's interface to manage customer-related and marketing tasks. Specifically, I move from the dashboard to the customers section, then to the marketing section to handle pending reviews. I select a particular review for editing and save the changes, indicating a workflow focused on reviewing and managing customer feedback. Each step is methodical, aimed at updating and maintaining the site's content and customer interactions.
|
||
|
||
---
|
||
|
||
## Part 2
|
||
### Step-by-Step Actions in the Video Segment
|
||
|
||
#### 1. **Action:** I click on the "Save Review" button.
|
||
- **Page Changes:** The page displays a notification at the top stating, "You saved the review."
|
||
- **Possible Purpose:** The likely intent is to save any changes made to the review details, ensuring that the updated information is stored in the system.
|
||
|
||
#### 2. **Action:** I click the back arrow located near the top left of the screen.
|
||
- **Page Changes:** The page transitions from the "Edit Review" screen to the "Pending Reviews" list view.
|
||
- **Possible Purpose:** The purpose is to return to the list of reviews, possibly to manage or edit another review.
|
||
|
||
#### 3. **Action:** I click on the "Edit" link next to the review for the product "Olivia 1/4 Zip Light Jacket."
|
||
- **Page Changes:** The page navigates to the "Edit Review" screen for the selected review.
|
||
- **Possible Purpose:** The intent is to modify the details of this specific review, such as the status, rating, or content.
|
||
|
||
#### 4. **Action:** I select the "Approved" option from the "Status" dropdown menu.
|
||
- **Page Changes:** The "Status" field updates to show "Approved."
|
||
- **Possible Purpose:** The goal is to change the review's status to "Approved," allowing it to be visible to other users on the website.
|
||
|
||
#### 5. **Action:** I click on the "Save Review" button.
|
||
- **Page Changes:** A notification appears at the top of the page stating, "You saved the review."
|
||
- **Possible Purpose:** The intention is to save the changes made to the review, specifically the updated status, ensuring the review is now approved and active.
|
||
|
||
### Summary
|
||
In this video segment, I perform a series of actions focused on managing product reviews. I save an edited review, navigate back to the list of pending reviews, select a specific review to edit, update its status to "Approved," and then save these changes. Each step is methodically executed to ensure the review is correctly modified and activated within the system.
|
||
|
||
---
|
||
|
||
## Part 3
|
||
### Step-by-Step Actions in the Video Segment
|
||
|
||
#### 1. **Action:** I click on the "Save Review" button.
|
||
- **Page Changes:** The page refreshes, and the review status updates to reflect the changes made.
|
||
- **Possible Purpose:** The likely intent is to save any modifications or approvals made to the review details. This action ensures that the changes are stored in the system.
|
||
|
||
#### 2. **Action:** I scroll up slightly to view the top section of the page.
|
||
- **Page Changes:** The upper part of the page becomes visible, showing the navigation menu and search bar.
|
||
- **Possible Purpose:** The purpose is to gain a better overview of the page layout or to access elements located at the top of the page, such as navigation options or filters.
|
||
|
||
#### 3. **Action:** I click on the "Back" button located near the top left of the review section.
|
||
- **Page Changes:** The page transitions back to the previous screen, which appears to be a list of reviews or a dashboard view.
|
||
- **Possible Purpose:** The intent is to return to the previous page, possibly to view other reviews or to perform additional tasks related to review management.
|
||
|
||
#### 4. **Action:** I hover over the "Marketing" menu item in the sidebar.
|
||
- **Page Changes:** A submenu expands, displaying various marketing-related options.
|
||
- **Possible Purpose:** The likely intent is to navigate to a specific marketing tool or feature. Hovering reveals the available options under the "Marketing" category for further selection.
|
||
|
||
#### 5. **Action:** I move the cursor away from the "Marketing" menu without selecting any submenu items.
|
||
- **Page Changes:** The submenu collapses, returning to the default sidebar view.
|
||
- **Possible Purpose:** The action suggests a momentary exploration of the menu options without the intention to select any specific feature at this time.
|
||
|
||
### Summary
|
||
In this video segment, my actions focus on saving a review, navigating back to a previous page, and briefly exploring the "Marketing" menu options. Each step is performed with the intent of managing reviews and potentially accessing additional tools, though no specific marketing feature is selected. The observed actions are straightforward and align with typical administrative tasks within a content management system.
|
||
|
||
# Playwright action
|
||
[
|
||
{
|
||
"action_uid": "link_\ue60b Sales",
|
||
"idx": 0,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"\ue60b Sales\")",
|
||
"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_\ue608 Catalog",
|
||
"idx": 1,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"\ue608 Catalog\")",
|
||
"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_\ue603 Customers",
|
||
"idx": 2,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"\ue603 Customers\")",
|
||
"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_\ue609 Marketing",
|
||
"idx": 3,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"\ue609 Marketing\")",
|
||
"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_Pending Reviews",
|
||
"idx": 4,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"Pending Reviews\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/admin/dashboard/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "cell_Apr 24, 2023, 2:53:49 PM",
|
||
"idx": 5,
|
||
"action_repr": "frame.clickget_by_role(\"cell\", name=\"Apr 24, 2023, 2:53:49 PM\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/352/ret/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/pending/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "cell_OKish",
|
||
"idx": 6,
|
||
"action_repr": "frame.clickget_by_role(\"cell\", name=\"OKish\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/349/ret/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/pending/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "button_\ue626 Back",
|
||
"idx": 7,
|
||
"action_repr": "frame.clickget_by_role(\"button\", name=\"\ue626 Back\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/349/ret/pending/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "cell_Quite good",
|
||
"idx": 8,
|
||
"action_repr": "frame.clickget_by_role(\"cell\", name=\"Quite good\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/347/ret/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/347/ret/pending/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "action_9",
|
||
"idx": 9,
|
||
"action_repr": "frame.selectOptionget_by_label(\"Status\", exact=True)",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/347/ret/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/347/ret/pending/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "button_Save Review",
|
||
"idx": 10,
|
||
"action_repr": "frame.clickget_by_role(\"button\", name=\"Save Review\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/347/ret/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/347/ret/pending/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "cell_seam miller",
|
||
"idx": 11,
|
||
"action_repr": "frame.clickget_by_role(\"cell\", name=\"seam miller\")",
|
||
"before": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/edit/id/349/ret/pending/"
|
||
},
|
||
"after": {
|
||
"url": "http://ec2-3-133-227-75.us-east-2.compute.amazonaws.com:7780/admin/review/product/pending/"
|
||
}
|
||
}
|
||
]
|
||
|
||
# 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" : [
|
||
]
|
||
}]
|
||
``` |