| Index | Functional module | Test case name | Test case type | Priority | Precondition | Step description | Expected result | Remarks |
|---|---|---|---|---|---|---|---|---|
| 1 | Code/repository list | Verify repository batch operation-modify status to pause successfully | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Multiple repositories with "Start" state already exist |
1. Click the 'Batch Operations' button, select 'Modify Status' -- change to 'Paused', select multiple repositories with 'Started' status, click the submit button 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Modification successful, repository status changed to "Paused" |
|
| 2 | Code/repository list | Verify the repository batch operation - successfully change status to closed | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Multiple repositories with "Start" state already exist |
1. Click the [Batch Operation] button, select 'Modify Status' - change to 'Closed', select multiple repositories in 'Started' state, click the Submit button 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Modification successful, repository status changed to 'Closed' |
|
| 3 | Code/repository list | Verify that the batch operation of repositorys to change the status to 'Start' is successful | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Repository with multiple 'Paused' statuses already exists |
1. Click the 'Batch Operation' button, select 'Modify Status' - change to 'Start', select multiple repositories in 'Pause' status, and click the submit button. 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Modification successful, repository status changed to "Started" |
|
| 4 | Code/repository list | Verify batch operation - transfer repository to enterprise successfully | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There are already multiple companies |
1. Click the "Batch Operations" button, select "Transfer Repository" - "Transfer to Enterprise", select the repository, select the enterprise, and click the submit button. 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Transfer successful, repository ownership is correct |
|
| 5 | Code/repository list | Verify successful batch operation - transfer repository to team | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There are multiple repositories under multiple teams |
1. Click the "Batch Operation" button, select "Transfer Repository"--"Transfer to Team", select multiple repositorys, and click the submit button. 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Transfer successful, repository ownership is correct |
|
| 6 | Code/repository list | Successfully verify batch operation - modify the responsible person | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Multiple repositories already exist |
1. Click the "Batch Operation" button, select "Modify Owner"--"Owner", select multiple repositorys, and click the submit button. 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Modification successful, repository owner changed correctly |
|
| 7 | Code/repository list | Verify batch operation - successfully change visibility to "private" | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Multiple 'Internal Open Source' repositories already exist |
1. Click the "Batch Operation" button, select "Modify Visibility" - "Private", select multiple internal open source repositories, and click the submit button 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Modification successful, repository visibility changed to private |
|
| 8 | Code/repository list | Verify that the batch operation to change visibility to 'Internal Open Source' is successful. | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There are multiple 'private' repositories |
1. Click on the 'Batch Operations' button, select 'Modify Visibility' - 'Internal Open Source', select multiple 'Private' repositories, and click the submit button. 2. Enter the administrator password and click the "OK" button |
1. Verify sensitive operation 2. Modification successful, repository visibility changed to internal open source |
|
| 9 | Code/repository list | Successful clearing of repository in batch operation | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Multiple repositories already exist |
1. Click the [Bulk Operations] button, select 'Clear Repository', select multiple repositories, and click the submit button. 2. Enter administrator password, click on 'Clear' button |
1. Verify sensitive operation 2. Successfully modified, repository is empty |
|
| 10 | Code/repository list | Verify successful deletion of repositories in batch operations | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Multiple repositories already exist |
1. Click on the [Batch Actions] button, select 'Delete Repository', select multiple repositories, and click the submit button. 2. Enter the administrator password, select 'Also delete tasks related to the associated repository', and click the 'Delete' button |
1. Verify sensitive operation 2. Delete repository successfully, repository-related tasks are deleted |
|
| 11 | Code/repository list | Verify Repository Inventory Display Data Correctly | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is a repository 'abc' with at least 1 pull request. |
View the displayed repository name, number of PRs, creator, creation time, and repository size. | Data correct | |
| 12 | Code/repository list | Validate filtering repository inventory - Project | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page There is already a repository called 'abc' belonging to the 'ABC' project, and a repository called 'aaa' that does not belong to any project. |
Click the "Projects" button 2. Select project 'ABC' |
1. Display project dropdown box 2. Correctly search for the target repository "abc" |
|
| 13 | Code/repository list | Validate repository inventory filter - class | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page There is already a repository called 'abc' belonging to the 'ABC' class, and a repository called 'aaa' that does not belong to any class. |
1. Click on the 'Class' button 2. Select project 'ABC' |
1. Display project dropdown box 2. Correctly search for the target repository "abc" |
|
| 14 | Code/repository list | Verify repository list filtering - responsible person | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a repository called "abc" with a manager named "aa", and a repository called "aaa" with a manager named "bb". |
1. Click on "Responsible Person" button 2. Select the owner as "aa" |
1. Display project dropdown box 2. Correctly search for the target repository "abc" |
|
| 15 | Code/repository list | Validate repository list filtering - type | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There are existing repositories "aa11", "aa22", "aa33", with types private/internal/outsourced respectively. |
1. Click the "Type" button 2. Select private 3. Select internal source 4. Select outsourcing |
1. Display project dropdown box 2. Successfully search for the target repository 'aa11' 3. Successfully search for the target repository 'aa22' 4. Correctly search for the target repository 'aa33' |
|
| 16 | Code/repository list | Verify repository inventory filter - keyword | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Repository 'aa11bb' already exists |
1. In the search input box, type: aa 2. In the search input box, type: bb 3. In the search input box, enter: 11 4. In the search input box, enter: AA |
1. Correctly search for the target repository: aa11bb 2. Correctly search for the target repository: aa11bb 3. Correctly search for the target repository: aa11bb 4. Correctly search for the target repository: aa11bb |
|
| 17 | Code/repository list | Verify setting/unsetting a repository as a template repository is successful | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Select a repository, click "..." 2. Click the 'Set as Template Repository' button 3. Click on the 'Create Repository' button in the top right corner of the list page 4. Click on the 'Use Template Repository' option 5. Pull down to view 6. Go back to the repository list, select a template repository, and click '...' 7. Click "Cancel Template Repository" option |
1. There is an option in the drop-down list of operations to set as a template repository 2. Refresh the list page, the repository name is displayed on the right with the "Template Repository" identifier 3. Redirect to the new repository page 4. Select template repository option box appears 5. The repository appears in the options 6. The drop-down list of operations includes the option to 'Cancel Template Repository'. 7. The identification of the repository 'Template Repository' disappears when the page is refreshed |
|
| 18 | Code/repository list | Validate jump to add member page | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click the "Add Member" button |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Successfully redirected to the 'Repository-Management-Member Management' page without error |
|
| 19 | Code/repository list | Verify redirection to code review page | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click [Request Review] |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Successfully jump to 'Repository-Code Review' page without error |
|
| 20 | Code/repository list | Verify view empty repository operation options | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already an empty repository A |
Select repository A and click "..." | The drop-down box displays the options of 'Add member', 'Create fork repository', 'Star', 'Function settings', 'Set protected branches', and 'Delete'. | |
| 21 | Code/repository list | Verify fork repository | Functional testing | P1 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click on "Create Fork Repository" 3. Select the fork object, click [OK] button 4. Go back to the 'Code - Repository List' page and check the statistics of the number of 'Forked Repositories' on the left. |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. The "Fork Repository" dialog box correctly displays the objects that can be forked 3. Go to the code page of the forked repository, the page does not report errors, and the repository name displays the 'Syncable' icon on the right. 4. The count of the forked repositories is increased by 1 |
|
| 22 | Code/repository list | Verify the prompt message for not selecting an object when forking a repository | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select empty repository A and click the '...' action 2. Click on "Create Fork Repository" 3. Do not select a fork object and click "OK" |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. The "Fork Repository" dialog box correctly displays the objects that can be forked 3. Prompt: Please select the owner of the Forked repository |
|
| 23 | Code/repository list | Verify starred repository | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click on 'Star' 3. On the 'Code - Repository List' page, check the quantity statistics of the 'Starred Repositories' on the left side. |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. The page refreshes and a yellow highlighted star appears on the right side of the repository name 3. Increase the count of starred repositories by 1 |
|
| 24 | Code/repository list | Verify cancel starred repository | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a starred repository A |
1. Select repository A and click "..." 2. Click 'Unstar' 3. On the 'Code - Repository List' page, check the quantity statistics of the 'Starred Repositories' on the left side. |
1. The dropdown menu displays options such as 'Add Member,' 'Request Review,' 'Create Fork Repository,' 'Unstar,' 'Set as Template Repository,' 'Settings,' 'Protect Branches,' and 'Delete.' 2. Page refreshes, yellow highlight star on the right side of the repository name disappears 3. Quantity statistics of 'Starred repositories' - 1 |
|
| 25 | Code/repository list | Verify setting template repository | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click on [Set as Template Repository] 3. On the 'Code-Repository List' page, check the statistics of the 'Template Repositories' on the left. |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Refresh the page to see an orange 'Template Repository' label on the right side of the repository name 3. The number of template repositories is reduced by 1 |
|
| 26 | Code/repository list | Validate cancel template repository | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page 3. Template repository A already exists |
1. Select repository A and click "..." 2. Click [Cancel Template Repository] 3. On the 'Code-Repository List' page, check the statistics of the 'Template Repositories' on the left. |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Unstar Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Refresh the page and the orange 'Template Repository' label on the right side of the repository name disappears 3. The number of template repositories is reduced by 1 |
|
| 27 | Code/repository list | Verify redirect to function setting page | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click on [Function Settings] |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Successfully navigate to the 'Repository-Management-Function Settings' page without any errors |
|
| 28 | Code/repository list | Verify jump to protected branch page | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A |
1. Select repository A and click "..." 2. Click on [Set Protected Branches] |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Successfully redirected to the "Repository-Management-Protected Branches" page without errors |
|
| 29 | Code/repository list | Successfully verify delete repository | Functional testing | P1 | 1. Administrator account login 2. Enter the code - repository list page 3. There is already a non-empty repository A, and A repository has associated tasks. |
1. Select repository A and click "..." 2. Click 'Delete' 3. Check 'Delete associated tasks in the repository', enter the password of the current logged-in user, and click the [OK] button 4. "Code-Repository List" page, view the total count of [All] on the left side. 5. View tasks associated with the repository |
1. The dropdown menu displays options 'Add Member', 'Request Review', 'Create Fork Repository', 'Star', 'Set as Repository Template', 'Feature Settings', 'Set Protected Branches', and 'Delete'. 2. Pop-up 'Sensitive operation' 3. The popup disappears and displays a message: Delete successful 4. [All] quantity statistics -1 5. Cannot find the associated task |
|
| 30 | Code/repository list | Validate jump to "All" repository list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Check the quantity statistics |
1. By default, jump to the 'All' repository list 2. The quantity statistics are correct |
|
| 31 | Code/repository list | Verify the jump to the list of repositories "I'm responsible for" | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'My Responsible' 2. Check the quantity statistics |
1. Go to the list of repositories that I am responsible for 2. The quantity statistics are correct |
|
| 32 | Code/repository list | Verify search for 'Repositories I'm responsible for' | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'My Responsible' 2. Enter the repository name containing the current logged-in user as the assignee in the search box and press Enter |
1. Go to the list of repositories that I am responsible for 2. Search data is correct |
|
| 33 | Code/repository list | Verify searching for non-'My Responsible' repository | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'My Responsible' 2. Enter the keyword of a repository name with a responsible person that is not the currently logged in user in the search box and press the enter key |
1. Go to the list of repositories that I am responsible for 2. Search data is empty |
|
| 34 | Code/repository list | Verify that it redirects to the 'Repositories I'm Involved In' repository list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'Participated by me' 2. Check the quantity statistics |
1. Go to the list of repositories I participate in 2. The quantity statistics are correct |
|
| 35 | Code/repository list | Verify search for 'Repositories I'm involved in' | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'Participated by me' 2. Enter the keyword of the repository name in which the current logged-in user is participating in the search box, and press the enter key |
1. Go to the list of repositories I participate in 2. Search data is correct |
|
| 36 | Code/repository list | Verify searching for non-'Participated' repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'Participated by me' 2. Enter a keyword in the search box that is not related to any repositories the current logged-in user is participating in, and press the enter key |
1. Go to the list of repositories I participate in 2. Search data is empty |
|
| 37 | Code/repository list | Verify the number of repositories in the 'Starred Repositories' section | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Starred Repositories' 2. Check the quantity statistics |
1. Go to the 'Starred Repositories' inventory 2. The quantity statistics are correct |
|
| 38 | Code/repository list | Validate searching for 'Starred Repository' repository | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Starred Repositories' 2. Enter the keyword of a starred repository name in the search box and press the enter key |
1. Go to the 'Starred Repositories' inventory 2. Search data is correct |
|
| 39 | Code/repository list | Verify searching for non-starred repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Starred Repositories' 2. Enter the keyword of a starred repository name in the search box and press the enter key |
1. Go to the 'Starred Repositories' inventory 2. Search data is empty |
|
| 40 | Code/repository list | Verify jump to the 'Template Repository' repository list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Template Repository' 2. Check the quantity statistics 3. Check the data in the repository list of the "Template Repository" |
1. Navigate to "Template Repository" inventory 2. The quantity statistics are correct 3. The repository name does not have an orange 'Template Repository' label on the right |
|
| 41 | Code/repository list | Validate searching for 'Template Repository' repository | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Template Repository' 2. Type the keywords of the template repository name in the search box and press the enter key |
1. Navigate to "Template Repository" inventory 2. Search data is correct |
|
| 42 | Code/repository list | Verify searching for non-template repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Template Repository' 2. Enter a keyword in the search box that is not a template repository name and press the enter key. |
1. Navigate to "Template Repository" inventory 2. Search data is empty |
|
| 43 | Code/repository list | Verify jump to create repository page | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Template Repository' 2. Choose a template repository and click 'Create repository' |
1. Navigate to "Template Repository" inventory 2. Jump to the "New repository" page, with the option "Use template repository" checked by default, and the template repository defaults to show this repository name. |
|
| 44 | Code/repository list | Verify the jump to the "Forked Repositories - All" repository list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 【Fork Repository】 2. Check the quantity statistics |
1. Go to the 'Forked Repositories - All' repository list. 2. The quantity statistics are correct |
|
| 45 | Code/repository list | Verify the navigation of the repository list of 'Forked Repositories - Repositories I Forked'. | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 【Fork Repository】 2. Click on [Forked by Me] |
1. Go to the 'Forked Repositories - All' repository list. 2. Go to the "Forked Repositories - Repositories I have forked" repository list |
|
| 46 | Code/repository list | Validate searching Forked repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 【Fork Repository】 2. Enter the keyword of the fork repository name in the search box and press enter |
1. Go to the 'Forked Repositories - All' repository list. 2. Search data is correct |
|
| 47 | Code/repository list | Verify search for non-Fork repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 【Fork Repository】 2. Enter the keyword of the non-fork repository name in the search box and press enter |
1. Go to the 'Forked Repositories - All' repository list. 2. Search data is empty |
|
| 48 | Code/repository list | Verify the jump to 'Paused and Closed Repositories-Pause' repository list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Paused and Closed Repositories' 2. Check the quantity statistics |
1. Jump to the "Pause" repository list 2. The quantity statistics are correct |
|
| 49 | Code/repository list | Verify the switch of the "Paused and Closed Repositories-Closed" repository list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Paused and Closed Repositories' 2. Click 'Close' |
1. Jump to the "Pause" repository list 2. Jump to the "Close" repository list |
|
| 50 | Code/repository list | Verify search for paused repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Paused and Closed Repositories' 2. Enter the keyword of a repository name in paused state in the search box and press Enter. |
1. Jump to the "Pause" repository list 2. Search data is correct |
|
| 51 | Code/repository list | Verify search for non-paused repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Paused and Closed Repositories' 2. Enter a keyword of a non-paused repository name in the search box and press enter. |
1. Jump to the "Pause" repository list 2. Search data is empty |
|
| 52 | Code/repository list | Verify the search closed state of the repository | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Paused and Closed Repositories' 2. Click 'Close' 3. Enter the keyword of the closed state repository name in the search box and press Enter |
1. Jump to the "Pause" repository list 2. Jump to the "Close" repository list 3. Search data is correct |
|
| 53 | Code/repository list | Verify search for non-closed repositories | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click on 'Paused and Closed Repositories' 2. Click 'Close' 3. Enter the keyword of the repository name in the search box for closed or paused status, press Enter key |
1. Jump to the "Pause" repository list 2. Jump to the "Close" repository list 3. Empty search data |
|
| 54 | Code/repository list | Verify search - fuzzy search | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Enter the repository name keyword in the search box and press the enter key |
1. By default, jump to the 'All' repository list 2. Page refreshes, returns all repositories containing the keyword |
|
| 55 | Code/repository list | Verify search - exact search | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Enter the full name of the repository in the search box and press the enter key |
1. By default, jump to the 'All' repository list 2. The page refreshes and the correct repository is searched |
|
| 56 | Code/repository list | Validate search - Case insensitive | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Enter the repository name in uppercase letters in the search box and press the enter key. |
1. By default, jump to the 'All' repository list 2. The page refreshes and shows all repositories containing the case-insensitive keyword |
|
| 57 | Code/repository list | Verify sorting - default sorting | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Click sorting icon |
1. By default, jump to the 'All' repository list 2. Dropdown option box displays 'default sorting', 'name sorting', 'creation time', 'update time', 'repository size', with 'default sorting' selected by default |
|
| 58 | Code/repository list | Verify sorting - name sorting | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Click sorting icon 3. Click the "Name Sorting". |
1. By default, jump to the 'All' repository list 2. Dropdown option box displays 'default sorting', 'name sorting', 'creation time', 'update time', 'repository size', with 'default sorting' selected by default 3. After the page refreshes, the repository name is sorted in the order of Chinese, English, and numbers. Chinese pinyin is sorted in reverse order, English is sorted in reverse order, and numbers are sorted in descending order |
|
| 59 | Code/repository list | Verify sorting - creation time | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Click sorting icon 3. Click【Create Time】 |
1. By default, jump to the 'All' repository list 2. Dropdown option box displays 'default sorting', 'name sorting', 'creation time', 'update time', 'repository size', with 'default sorting' selected by default 3. Refresh the page and sort by creation time in descending order |
|
| 60 | Code/repository list | Verify sorting - update time | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Click sorting icon 3. Click【Update Time】 |
1. By default, jump to the 'All' repository list 2. Dropdown option box displays 'default sorting', 'name sorting', 'creation time', 'update time', 'repository size', with 'default sorting' selected by default 3. Refresh the page and sort by update time in descending order |
|
| 61 | Code/repository list | Verify sorting - repository size | Functional testing | P2 | 1. Administrator account login 2. Enter the code - repository list page |
1. Go to Code-Repository list page 2. Click sorting icon 3. Click "Repository Size" |
1. By default, jump to the 'All' repository list 2. Dropdown option box displays 'default sorting', 'name sorting', 'creation time', 'update time', 'repository size', with 'default sorting' selected by default 3. Page refreshes and sorts the repositories by size from largest to smallest |
|
| 62 | Code/repository list | Successfully verify the jump to the 'open' code review list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click "Open" 2. Check the quantity statistics |
1. Jump to the 'open' code review list 2. The quantity statistics are correct |
|
| 63 | Code/repository list | Verify the switch between the "Merged" code review list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click 'Merged' 2. Check the quantity statistics |
1. Go to the 'Merged' code review list 2. The quantity statistics are correct |
|
| 64 | Code/repository list | Verify switching to the 'Closed' code review list | Functional testing | P3 | 1. Administrator account login 2. Enter the code - repository list page |
1. Click [Closed] 2. Check the quantity statistics |
1. Go to the "Closed" code review list 2. The quantity statistics are correct |