169 lines
7.4 KiB
Plaintext
169 lines
7.4 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
|
||
set the homepage URL on my GitLab profile to https://egg.tart.com
|
||
|
||
# Annotation description
|
||
### Step-by-Step Actions in the Provided Video Segment
|
||
|
||
#### 1. **Action:** I click on the "New project" button.
|
||
- **Page Changes:** A dropdown menu appears with options such as "Set status," "Edit profile," and "Sign out."
|
||
- **Possible Purpose:** The likely intent is to initiate the creation of a new project within GitLab. However, the action inadvertently opens a user account dropdown instead of directly proceeding to the new project setup page.
|
||
|
||
#### 2. **Action:** I move the cursor over the "Edit profile" option in the dropdown menu.
|
||
- **Page Changes:** No immediate changes occur other than highlighting the "Edit profile" option.
|
||
- **Possible Purpose:** This action suggests an intention to access the profile editing section, possibly to update personal information or settings related to the user account.
|
||
|
||
#### 3. **Action:** I click on the "Edit profile" option in the dropdown menu.
|
||
- **Page Changes:** The webpage transitions to the "Edit Profile" section under User Settings. This page includes fields for updating various profile details such as avatar, current status, time settings, main settings, and more.
|
||
- **Possible Purpose:** The intent is to modify or review the user's profile information. This could involve updating contact details, status messages, or other personal settings.
|
||
|
||
#### 4. **Action:** I scroll down to the "Time settings" section.
|
||
- **Page Changes:** The view shifts to display the "Time settings" area, which allows setting the local time zone.
|
||
- **Possible Purpose:** The goal might be to adjust the time zone setting to ensure accurate time-related information is displayed in the GitLab interface.
|
||
|
||
#### 5. **Action:** I click on the "Time settings" section.
|
||
- **Page Changes:** A modal or dialog box titled "Time settings" appears, allowing me to set my local time zone.
|
||
- **Possible Purpose:** The specific aim is to configure the local time zone, ensuring that all timestamps and schedules within GitLab are correctly aligned with the user's actual location.
|
||
|
||
#### 6. **Action:** I select a time zone from the dropdown menu in the "Time settings" modal.
|
||
- **Page Changes:** The selected time zone is applied, and the modal may close or show a confirmation message indicating the successful update.
|
||
- **Possible Purpose:** This finalizes the time zone configuration, making sure that all activities logged and displayed in GitLab reflect the correct local time for the user.
|
||
|
||
---
|
||
|
||
### Summary
|
||
In this video segment, I initially attempt to create a new project but accidentally access the user account dropdown. I then navigate to the "Edit profile" section to potentially update profile details. Subsequently, I focus on the "Time settings" to configure the local time zone, ensuring accurate time representation in the GitLab platform. Each step is driven by the objective of setting up or adjusting personal account settings within the GitLab environment.
|
||
|
||
# Playwright action
|
||
[
|
||
{
|
||
"action_uid": "user-menu",
|
||
"idx": 0,
|
||
"action_repr": "frame.clickget_by_test_id(\"user-menu\").get_by_role(\"link\", name=\"Byte Blaze\")",
|
||
"before": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/"
|
||
},
|
||
"after": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "link_Edit profile",
|
||
"idx": 1,
|
||
"action_repr": "frame.clickget_by_role(\"link\", name=\"Edit profile\")",
|
||
"before": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/-/profile"
|
||
},
|
||
"after": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "action_2",
|
||
"idx": 2,
|
||
"action_repr": "frame.clickget_by_placeholder(\"https://website.com\")",
|
||
"before": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/-/profile"
|
||
},
|
||
"after": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/-/profile"
|
||
}
|
||
},
|
||
{
|
||
"action_uid": "button_Update profile settings",
|
||
"idx": 3,
|
||
"action_repr": "frame.clickget_by_role(\"button\", name=\"Update profile settings\")",
|
||
"before": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/-/profile"
|
||
},
|
||
"after": {
|
||
"url": "http://metis.lti.cs.cmu.edu:8023/-/profile"
|
||
}
|
||
}
|
||
]
|
||
|
||
# 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" : [
|
||
]
|
||
}]
|
||
``` |