| Index | Function Module | Test Case Name | Test case type | Priority | Precondition | Step description | Expected result | Remarks |
|---|---|---|---|---|---|---|---|---|
| 1 | Repository settings/Repository member management | Bulk agree to the application list in the repository member management: Select all on this page and change the applicant's permissions to Reporter successfully. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Click on "Batch Operations" 2. Check [Select all on this page] 3. Bulk agree as 'reporter' 4. Click "Agree" |
1. Prompt: Successfully batch approved 20 requests! Member permissions changed from manager to reporter when applying. Add 20 people to the reporter page The status in the application list is 'Agreed' |
|
| 2 | Repository settings/Repository member management | Batch approve in the repository member management-application list: Select all and change the applicant's permission to observer successfully | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Click on "Batch Operations" 2. Check 'Select all' 3. Batch agree as [Observer] 4. Click "Agree" |
1. Prompt: Successfully approved 60 applications in batches! Changed member's permission from developer to reporter Increase 60 people on the observer page The status in the application list is 'Agreed' |
|
| 3 | Repository settings/Repository member management | Batch reject in the repository member management-application list: Select all on this page and change the applicant's permission to manager successfully | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Click on "Batch Operations" 2. Check [Select all on this page] 3. Batch agree as [Observer] 4. Click "Reject" |
1. Prompt: Successfully rejected 20 requests in batch! Update the status in the application list to 'Rejected' 2. null 3. null |
|
| 4 | Repository settings/Repository member management | Bulk reject in repository member management: Select all and change the applicant's permission to developer successfully | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Click on "Batch Operations" 2. Check 'Select all' 3. Batch agree as [Developer] 4. Click "Reject" |
1. Prompt: Successfully rejected 21 applications in bulk! Update the status in the application list to 'Rejected' 2. null 3. null |
|
| 5 | Repository settings/Repository member management | Repository member management - Cancel batch operation successful | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Click on "Batch Operations" 2. Check 'Select all' 3. Batch agree as [Developer] 4. Click "Cancel" |
1. Cancellation successful 2. null 3. null 4. null |
|
| 6 | Repository settings/Repository member management | Successfully approve/reject user application in repository member management | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Select the loris-7 user in the list and change the permission to Reporter, then click Agree 2. Select user Charlie from the list and click Reject |
1. Agree/Reject normally 2. null |
|
| 7 | Repository settings/Repository member management | 403 Forbidden error when a non-administrator tries to access the public key page in repository member management | Functional testing | P1 | 1. The repository already has developers, reporters, observers, and other permissions below administrators 2. Guest not logged in and logged in |
1. Use the developer account of the repository member: moyu, enter the URL for public key management and the URL for adding public keys in the browser https://gitee.ru/Alice/Python/deploy_keys https://gitee.ru/Alice/Python/deploy_keys/new 2. Use the guest user 'momo' to enter the URL for managing and adding public keys in the browser in both logged-in and logged-out states https://gitee.ru/Alice/Python/deploy_keys https://gitee.ru/Alice/Python/deploy_keys/new |
1. Access route with non-administrator permission 403 2. null |
|
| 8 | Repository settings/Repository member management | Repository Member Management-Application List: The filter status is displayed correctly, and the data is shown correctly when there is or no data. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of repository test-repo. |
1. Switch the status to Pending review, Approved, Rejected, Expired, Accepted invitation, All statuses in turn 2. Check if the data corresponds correctly when switching status |
1. All states of 'Pending Review', 'Approved', 'Rejected', 'Accepted Invitation' have data and the tree fern is correct 2. Expired with no data, displays: No data matching the criteria |
|
| 9 | Repository settings/Repository member management | Repository member management - Switch application list page | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of repository test-repo. |
1. Switch the status to Pending review, Approved, Rejected, Expired, Accepted invitation, All statuses in turn 2. 3. Check if the data corresponds correctly when switching status and switching pages |
1. Switch pagination data correctly 2. null 3. null |
|
| 10 | Repository settings/Repository member management | Repository member management-application list: search function is normal | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of repository test-repo. |
1. Enter a non-existent applicant name abc 2. Enter a non-existent personal space address 123 3. Enter the nickname you gave to the applicant Charlie 4. Enter the correct personal space address for Charlie 5. The nickname written by the user when applying for it is Frank 6. Enter the user's own nickname: Bob |
1. Enter a non-existent applicant's name - Page prompt: No data matching the condition 2. Enter a non-existent personal space address - Page prompt: No data matching the condition 3. Enter the nickname you gave to the applicant - the page displays the applicant's application record, but the name is displayed as the user's nickname 4. Enter the correct personal space address - the page displays all records for that user. 5. Enter the nickname that the user wrote when applying - the page displays all records of the user 6. Enter the user's own nickname - the page displays the records of the user with no remarks about their name. |
|
| 11 | Repository settings/Repository member management | Repository member management - Application list: The list correctly displays user avatar nickname, the remark filled in during application, application reason, application time, and application status. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of repository test-repo. |
1. Check if user avatar is normal 2. Check if there is a style error when viewing user application reasons for 200 characters 3. Check if the application time is correct 4. Check if the remarks when applying are displayed correctly 5. Display user nickname correctly when hovering over the user 6. Does the style error occur when the user nickname is too long |
1. The user avatar nickname, the remark filled in during the application, the application reason, the application time, and the application status are displayed correctly in the list. 2. null 3. null 4. null 5. null 6. null |
|
| 12 | Repository settings/Repository member management | Manage repository members - private repositories do not allow external member application | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Enable the switch 'Allow External Members to Apply for Joining' | 1. Failed to enable: Only public repositories can be enabled for applications | |
| 13 | Repository settings/Repository member management | Repository member management - User submission successful | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Access repository test-repo and click 'Apply to join repository'. 2. Fill in the name as Test Engineer 3. Fill in application reasons 4. Click [Submit] |
1. The application has been successfully submitted 5. Successfully closed, prompt 'Member Close Successful' in the upper right corner 2. null 3. null |
|
| 14 | Repository settings/Repository member management | Repository member management - User submission failed | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of private repository test-repo. |
1. Access repository test-repo and click 'Apply to join repository'. 2. Do not fill in the name 3. Fill in application reasons 4. Click [Submit] |
1. Submission failed: name and application reason are required fields 2. null 3. null 4. null |
|
| 15 | Repository settings/Repository member management | Repository Member Management - Search repositories in 'Invite Members to Repository' | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. Enter the [Invite through repository] page |
1. Enter the repository dvfd123/vdfvfdvfv 2. Enter repository vdfvfdvfv 3. Enter ???? |
Step 1.1 displays "No results found." 2.2 Match the repository dvfd123 / vdfvfdvfv Step 3.3 no results found |
|
| 16 | Repository settings/Repository member management | Repository member management-Invite members through repository: Automatically load and calculate the total number of members and the number of members joined normally | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. Enter the [Invite through repository] page |
1. Select a public repository with 40 members 2. Check if the selected total member data is consistent with the actual member data 3. Check if the members who have joined the target repository have the label "Joined" after their names and the color becomes gray |
1. The page displays: There are a total of 40 members, of which 10 have joined the target repository. 2. After joining, it is marked as 'Joined' and the color becomes gray 3. null |
|
| 17 | Repository settings/Repository member management | Repository Member Management - Send Invitation by Repository Invitation: No members in the repository | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. Enter the [Invite through repository] page |
1. Select a repository with only one member, and the member is also a member of the target repository 2. Click the "Send Invitation". |
1. The 'Send Invitation' button cannot be clicked and is in a disabled state 2. null |
|
| 18 | Repository settings/Repository member management | Repository Member Management - Send invitations to invite members through repository invitations: Private repository is full | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page |
For a public repository with 5 members, go to the 'Add Members' page and select a repository with 10 members to invite. 2. Open another browser tab and set the repository as private. 3. Switch to the 'Invite Members via Repository' page - select 3 members - click 'Send Invitation' |
1. Prompt: Failed to join, the current repository is full 2. null 3. null |
|
| 19 | Repository settings/Repository member management | Invite members through repository invitation: Deselect members during the repository adding process. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. The repository is public. |
1. Enter the repository invitation page - select a repository (with 2 members) 2. Uncheck the member "pig4" 3. Click on "Send Invitation" |
Step 1. The "Send Invitation" button is clickable. 2. Prompted that the invitation link has been successfully sent but it is not actually delivered This is an online bug |
|
| 20 | Repository settings/Repository member management | Successfully send an invitation to a member through repository invitation | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. The repository is public. |
1. Enter the repository invitation page - select a repository (with 2 members) 2. Check the member pig4 3. Click on "Send Invitation" |
1. Prompt that the invitation is sent successfully 2. null 3. null |
|
| 21 | Repository settings/Repository member management | Repository member management - invitation acceptance private message | Functional testing | P1 | 1. Repository test-repo has sent an invitation to pig4. Step 2. pig4 logs in to gitee. |
1. Check if invitation message is displayed correctly 2. After clicking 'Confirm Join', a confirmation box pops up 3. Click accept |
1. Private message invitation is: Bob invites you to join the test-repo repository, confirm to join 2. After accepting, enter the repository homepage 3. null |
|
| 22 | Repository settings/Repository member management | There is no data in the repository member management application list. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob goes to the member management - requests list of repository test-repo. |
1. Open application list | 1. No member applications | |
| 23 | Repository settings/Repository member management | View invitation details after submitting 'Add members directly' in repository member management: Non-empty email users. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the repository member management - add repository members page 3. Enter personal git address (the user has not publicly shared the email address), user permission is set to 'Reporter'. 4. After adding, click 'Submit' |
1. Check the invitation details box for correct member information (user email, user nickname, personal space address, repository permissions, user status, invitation result). 2. Click 'Close' invitation details box |
1. Invitation details display user email, user nickname, personal space address, repository permissions, user status, invitation result correctly (eg: **** Testing git reporter gitee user has sent the invitation link via private message) 2. null |
|
| 24 | Repository settings/Repository member management | Manage repository members - Add yourself as a developer to the public repository [Directly add members] | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the repository member management - add repository members page 3. Enter the personal address Bob (the user's email address is not public), and the user's permission is set as a developer 4. After adding, click 'Submit' |
1.1 Permission to view invitation details 2. View invitation details invitation result |
1. Invitation details information is correct 2. The invitation result shows: the user is already a member of the repository |
|
| 25 | Repository settings/Repository member management | Repository member management - the recipient joins the repository by accepting an expired invitation via private message | Functional testing | P1 | ||||
| 26 | Repository settings/Repository member management | Manage repository members - acceptor rejects joining the repository | Functional testing | P1 | 1. Bob has invited the user logis by directly adding members and sending invitation messages. 2. log in to Gitee using logis |
Step 1. Check if there is an invitation private message in the notifications. 2. Click invitation link 3. Cancel invitation |
1. Invite message correctly displayed: Bob invites Nana Zi to join the public repository Product Group/nmlgb and confirms the invitation After clicking the confirm join link, click cancel to succeed |
|
| 27 | Repository settings/Repository member management | Repository member management - The recipient joins the repository through private messaging | Functional testing | P1 | 1. Bob has invited the user logis as an administrator by directly adding the member and sending a private message invitation 2. log in to Gitee using logis |
Step 1. Check if there is an invitation private message in the notifications. 2. Click the "Confirm Join" button 3. Accept invitation |
Step 1. Prompt: You have successfully joined the repository. 2. null 3. null |
|
| 28 | Repository settings/Repository member management | Repository member management - Private repository [Directly add members] directly add the member as a repository member | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. Enter personal address poni (the user has not disclosed the email address), user permission is developer 4. After adding, click 'Submit' |
1. Check if the information on the invitation details page is correct 2. Click [Close] |
1. Private repository members directly add members 2. Invitation result shows joined repository |
|
| 29 | Repository settings/Repository member management | Repository member management - [Invite to Repository] page, the select box displays the repository data correctly | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the test-repo member management page 3. Enter the [Invite through repository] page |
1. Compare the repository data in the dropdown with the data in the personal workspace to see if they are consistent 2. When the repository name is too long, there is no overflow or line break in the dropdown, etc. 3. The repository ownership is correct (including organization and enterprise) |
1. Repository data is correct 2. Normal style 3. null |
|
| 30 | Repository settings/Repository member management | Repository member management - Repository [Directly add members] enter the other email of the user with a non-public email | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page 4. Enable 'Do not make my email address public' in the user's personal settings |
1. Enter loris' email (submission email, notification email, primary email, or other email): submission email [email protected] 2. Check the search results in the dropdown |
1. The search result shows: [email protected] (non-public email user), no user avatar and nickname information 2. null |
|
| 31 | Repository settings/Repository member management | Failed to transfer private repository to user. The recipient declined in the transfer notification list. | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page 4. Search for the public email address of the git object |
1. Enter a non-commit and primary email for git: momo@123. com 2. Check the search results in the dropdown |
1. The search results display the user's email address, nickname, and personal address, e.g., Super Admin (git) 2. null |
|
| 32 | Repository settings/Repository member management | Add members directly to the repository [input] with an inactive email | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page 4. Just registered enterprise user: manta |
1. Enter email: [email protected] 2. Check the search results in the dropdown |
1. The search results should accurately match the user's avatar, nickname, and personal address 2. null |
|
| 33 | Repository settings/Repository member management | Manage repository members - Add 100 users to the repository simultaneously | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page |
1. Select 100 members: among them, the member nickname is about 150 characters 2. Check the style of the member with a long nickname in the dropdown 3. Check the style and whether the input box overflows for 100 members |
1. Avatar style is normal with no overflow issues 2. null 3. null |
|
| 34 | Repository settings/Repository member management | Member Management of Repository - In the confirmation box for removing members, changing role permissions, accessing members is normal for public repositories. | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page 4. Enter personal address/email address and select 20 members, click [Add] 5. Change repository permission to manager |
1. Check the member confirmation box to add 20 member information (avatar, personal address, nickname) 2. Click on the member 'blue' in the [Members] column to check if the jump is successful 3. Change the role permission of a member in the [Repository Role Permissions] column to Administrator (default is Developer) Successfully remove member poni in the [Action] column 5. null |
1. The member information is normal in the add member confirmation dialog 2. Click on the member to jump to the member's personal homepage 3. Successfully change member's repository role permissions 4. Remove member normally 5. Add member list is too long and scroll bar appears |
|
| 35 | Repository settings/Repository member management | Add empty user to the repository member management - Public repository [Directly add member] | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the repository member management - add repository members page 3. Enter personal address or email address, select 5 members, click 'Add' 4. Invite permission as developer |
Step 1. Add a member named loris. 2. Remove the member from the add member confirmation dialog 3. Click [Submit] |
1. Prompt: Please select a user before continuing 2. null 3. null |
|
| 36 | Repository settings/Repository member management | Successfully send invitation message after submitting the member management of the repository 'pink' as a public repository [directly add members], and the invitation details are correct: Public email user. | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the repository member management - add repository members page 3. Enter personal address or email address to select 5 members, add them and then click [Submit] 4. Invite permission as developer |
1. Check the invitation details box for correct member information (user email, user nickname, personal space address, repository permissions, user status, invitation result). 2. Clicking on the user logis' nickname will redirect to logis' personal homepage 3. Click [Close] on the invitation details box |
1. The invitation details box correctly displays the user's email, nickname, personal space address, repository permissions, user status, and invitation result. Example: ([email protected], nanazi, nanazi, Developer, Gitee user, invitation link has been sent via private message) 2. Click on a specific user's nickname in the user nickname column to correctly navigate to their personal workspace. 3. Successfully close the invitation details box |
|
| 37 | Repository settings/Repository member management | Manage expired invitation links in repository member management | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Link invitation |
1. The link is an expired link: https://gitee.ru/Alice/else/invite_link?invite=XXX | 1. Prompt: Invalid link 2. null |
|
| 38 | Repository settings/Repository member management | Test cases related to the invitation link becoming invalid after changing the invitee conditions in repository member management | Functional testing | P1 | ||||
| 39 | Repository settings/Repository member management | Repository member management - User invites themselves via QR code or link | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page |
1. kabenka copies the link and opens it, QQ, and WeChat scan the QR code | 1. Prompt: You are already a repository member | |
| 40 | Repository settings/Repository member management | Repository member management-view the notification of the invitee receiving an internal message (enable audit function) | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Link invitation, QR code |
1. Send the invitation link and QR code to two users separately, who have repository permissions as developers: Blue and Poni. 2. blue and poni accept the invitation respectively 3. Bob views the notification private message page |
1. Bob notification shows: blue applies to join the test-repo repository, view details poni has requested to join repository test-repo. View details. 2. null |
|
| 41 | Repository settings/Repository member management | Repository Member Management - Public Repository [Directly Add Members]: Enter a non-Gite user in the input bar | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page |
1. Entered personal address is unregistered: bluelbuelfee 2. Click [Add] |
1. After entering an unregistered personal address, the dropdown prompts 'No matches found', and the dropdown is collapsed and the personal address is cleared. 2. null |
|
| 42 | Repository settings/Repository member management | Manage repository members - Public repository [Add members directly] Enter an unregistered email in the input field | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page |
1. Enter the unregistered email [email protected] | 1. The search result in the dropdown displays one or more keywords as an internal match, for example: Zhang San (vip.com) | |
| 43 | Repository settings/Repository member management | Repository member management - View user avatar and nickname in dropdown after entering personal address | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page |
1. Enter the user's personal address: CNTY 2. Check if the user's nickname, avatar, personal address, and search content are the same in the dropdown |
1. Enter a personalized address, members matching CNTY will appear in the dropdown (case insensitive) 2. The user's avatar and nickname should match their personal homepage |
Public repositories are the same as private repositories |
| 44 | Repository settings/Repository member management | Repository member management - Add members directly - Enter a non-public email address in the input field | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Go to direct add page |
1. Enter non-public email address (user has enabled 'Do not make my email address public'): [email protected] 2. Check the search results in the dropdown |
1. Search results display: [email protected] (non-public email user) without user avatar and nickname information 2. null |
|
| 45 | Repository settings/Repository member management | Manage repository members - Use QR code to invite repository members (with audit function) - QQ users | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page |
Step 1. Switch the repository permission to administrator. 2. Non-member lobobo2 outside the repository uses QQ to scan-QQ is already bound to Gitee 3. lobobo2 checks if the invitation information in the confirmation box is correct 4. Click 'Accept Invitation' |
1. Return to personal workspace and prompt: Confirmation successful, waiting for administrator review 2. null 3. null 4. null |
|
| 46 | Repository settings/Repository member management | Repository member management - Share to QQ to invite non-logged-in users - Audit not enabled | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page |
1. Switch repository permission to administrator 2. Share to QQ, open the link by QQ user 3. QQ users check if the invitation link in the confirmation box is correct 4. Click 'Accept Invitation' 4 |
1. The qq invitation information is: invite you to join my repository 2. After the user clicks accept, they need to log in successfully to enter the repository 3. null 4. null |
|
| 47 | Repository settings/Repository member management | Repository member management - Share with QQ invite login users (audit not enabled). | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Send the QQ invitation link text correctly |
1. Switch repository permission to developer 2. Share to QQ, QQ user has logged in gitee and opened the link 3. Check if the QQ user confirms the invitation information in the confirmation box is correct. 4. Click 'Accept Invitation' |
1. The repository path in the invitation message (Bob/test-repo), inviter (Bob), and repository permission (Reporter) are displayed correctly 2. Accept the invitation and go to the repository homepage 3. null 4. null |
|
| 48 | Repository settings/Repository member management | Repository member management - Share with qq invitation for non-logged in users (enable review) | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Send the QQ invitation link text correctly |
1. Switch repository permission to reporter 2. Share to QQ, open the link in QQ without logging in. 3. Check if the QQ user confirms the invitation information in the confirmation box is correct. 4. Click 'Accept Invitation' |
1. The repository path in the invitation message (Bob/test-repo), inviter (Bob), and repository permission (Reporter) are displayed correctly 2. After accepting the invitation, it redirects to the login page. After successful login, it redirects to the personal dashboard and shows a message 'Confirmation successful, waiting for administrator approval' 3. null 4. null |
|
| 49 | Repository settings/Repository member management | Repository member management - Share to QQ and invite login user (with approval enabled) | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Send the QQ invitation link text correctly |
1. Switch repository permission to reporter 2. Share to QQ, open the link after logging in with QQ user 3. Check if the QQ user confirms the invitation information in the confirmation box is correct. 4. Click 'Accept Invitation' |
1. The repository path in the invitation message (Bob/test-repo), inviter (Bob), and repository permission (Reporter) are displayed correctly 2. Accept the invitation and go to the personal dashboard, and receive a prompt: Confirmation successful, waiting for administrator approval. 3. null 4. null |
|
| 50 | Repository settings/Repository member management | Repository member management - use old link to invite after enabling forced review | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Links applied without enabling review and forced review 4. Link is not expired |
1. Bob gets the invitation link (which is one day old) and enters the correct invitation code in the browser: https://gitee.ru/Alice/else/invite_link?invite=XXX | 1. Return to personal workspace and prompt: Confirmation successful, waiting for administrator review 2. null 3. null 4. null |
|
| 51 | Repository settings/Repository member management | Repository member management - Inviting the same user multiple times with different repository permissions | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the test-repo member management page 3. Link invitation |
1. Get the invitation link (QR code) for the administrator, developer, reporter, and observer respectively, and send it to members outside the repository, momo. 2. Copy the link provided by momo and open it in a browser, then accept the invitation |
1. If the same user is repeatedly invited after enabling the review function, the prompt 'Your application has not been processed by the administrator, please do not reapply' should be shown. 2. null |
|
| 52 | Repository settings/Repository member management | Repository member management-Invite users to become administrators through links (without enabling review): the recipient rejects the invitation | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository members - add repository members page |
1. Bob selects repository permission as administrator and clicks "Copy Link" to send it to external member Charlie. 2. Charlie gets the invitation code and enters the correct invitation code in the browser: https://gitee.ru/Alice/test-repo/invite_link?invite=XXX |
1. Confirm that the repository inviter, repository permissions, and repository information in the dialog are correct Step 2. After cancellation, the current invitation repository page. 3. null 4. null |
|
| 53 | Repository settings/Repository member management | Repository Member Management - Invite Unregistered Users via Link (No Approval Enabled) | Functional testing | P1 | 1. Warehouse administrator Bob is logged in. 2. Bob enters the repository member management - add repository members page |
1. Bob selects repository permission as administrator and clicks "Copy Link" to send it to external member Charlie. 2. Charlie gets the invitation code without logging in and enters the correct invitation code in the browser: https://gitee.ru/Alice/test-repo/invite_link?invite=XXX |
1. After an unauthenticated user clicks [Accept], they will be redirected to the login page and enter the repository homepage after successful login. 2. null 3. null 4. null |
|
| 54 | Repository settings/Repository member management | Repository member management - Enable administrator review function | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository members - add repository members page |
1. Check the option 'Requires administrator review' 2. Background of the text changes 3. Check if the invitation link is updated for the reporter in the repository permissions after checking the function |
1. The invitation link refreshes after selecting 'Require admin approval' Step 2. The background color changes from red to yellow. 3. null |
|
| 55 | Repository settings/Repository member management | Repository member management - Invite users to become repository reporters via links (enable administrator review) | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository members - add repository members page 3. Audit function has been enabled |
1. Bob clicks "Copy Link" to send the invitation code to Bob, who is outside the repository 2. Bob gets the invitation code and enters the correct invitation code in the browser: https://gitee.ru/Alice/test-repo/invite_link?invite=XXX |
1. Return to personal workspace and prompt: Confirmation successful, waiting for administrator review 2. null 3. null 4. null |
|
| 56 | Repository settings/Repository member management | Repository member management - Invite repository members using QR code (without enabling review function) - qq not logged in. | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository member management for eles - add repository member page |
Step 1. Switch the repository permission to observer. 2. Use QQ (not linked to Gitee account) to scan the code 3. Check if the invitation information in the confirmation box is correct 4. Click 'Accept Invitation' |
1. The role invited is an observer: Bob invites you to join the repository as a reporter. 2. Repository information is displayed correctly: Bob/test-repo and the description is normal 3. Click [Accept Invitation] to go to the login page, login and enter the repository page 4. null |
|
| 57 | Repository settings/Repository member management | Repository member management - invites repository members using QR code (without enabling approval function) - scans QR code with WeChat (binded with Gitee) | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. kanbenka enters the test-repo member management page |
Step 1. Switch the repository permission to reporter. 2. Member lobobo2, who is outside the repository, uses WeChat to scan the QR code - WeChat is already bound to Gitee 3. Click 'Accept Invitation' |
1. The invited role is reporter: Bob invites you to join the repository as a reporter 2. Repository information is displayed correctly: Bob/test-repo and the description is normal 3. After clicking [Accept Invitation], it redirects to the repository homepage |
|
| 58 | Repository settings/Repository member management | Access the repository member management page with the wrong route in the repository member management | Functional testing | P1 | 1. Warehouse administrator Bob 2. Logged in state |
In the browser address bar, enter respectively: https://gitee.ru/Alice/test-repo/teams https://gitee.ru/Alice/test-repo/team?type=mastersssss https://gitee.ru/Alice/test-repo/team_members/apply_lisssst |
1. Accessing an error route does not throw errors in the console or on the page. The page returns 404. | |
| 59 | Repository settings/Repository member management | Repository Member Management - Admin accesses all pages in the Repository Member Management | Functional testing | P1 | 1. Warehouse administrator Bob 2. Logged in state |
In the browser address bar, enter respectively: https://gitee.ru/Alice/test-repo/team https://gitee.ru/Alice/test-repo/team?type=masters https://gitee.ru/Alice/test-repo/team_members/apply_list |
1. Accessing the route as an administrator will correctly redirect to the 'All', 'Administrator', 'Application' list pages | Reporters and observers are the same, no need to repeat. |
| 60 | Repository settings/Repository member management | Compatibility of repository member management - repository member management page | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository member management page. 3. Public and private repositories |
1. Open the member management page of public repository A and private repository B in Chrome, Firefox, Edge, 360, etc. 2. Switch internationalization in different browsers 3. Check if there is any overflow of the text description in different localizations outside the text box 4. Different internationalization, buttons, dropdowns, and input boxes have correct Chinese text and do not overflow or wrap |
1. Public/Private repositories have correct internationalization expressions in different browsers, and the component text and styles are normal 2. null 3. null 4. null |
|
| 61 | Repository settings/Repository member management | Repository member management - Click on role permission instructions | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository member management page. 3. Repository already has members |
1. Member list (can be all, admins, viewers, reporters, developers pages) 2. Click on the role next to? |
1. Successfully navigate to the help center 2. null |
|
| 62 | Repository settings/Repository member management | Repository Member Management - Check the default permission of the invitation role | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository member management - add repository member page |
1. The default display of the invitation repository permission in the select is developer 2. Directly added repository permissions are displayed as developers by default 3. Add member Bob from repository YU |
1. The repository permission on the link invitation and direct member addition page is displayed as "developer" by default. 2. Members added from the repository are displayed in the list with the developer permission. 3. null |
|
| 63 | Repository settings/Repository member management | Switch repository permissions in the repository member management | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository member management - add repository members page |
1. Switch from the default display of developers to administrators, and check if the invite code in the link address has changed. Copy the link and open it in a browser to check if the invited role is reported as a reporter. 2. Switch from administrator to reporter, check if the invitation code changes and copy the link. Bob uses the link to open it in a browser and check if the invited role is a reporter. 3. Switch from administrator to observer, check if the link address invite code has changed and copy the link. Bob uses the link to open it in the browser and checks if the invitation role is an observer. |
1. After switching different role permissions, the invitation code in the invitation link changes accordingly, and the role in the invitation repository member confirmation box for the invitee is correct, and the QR code is refreshed 2. null 3. null |
|
| 64 | Repository settings/Repository member management | Repository member management - invite user as developer via link: incorrect invitation link | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. kabeka enters the repository member management page 3. Go to the link invitation page |
1. Bob clicks "Copy Link" to send the invitation code to Bob, who is outside the repository 2. Bob gets the invitation code and enters the last three codes incorrectly in the browser: https://gitee.ru/Alice/test-repo/invite_link?invite=XXX |
1. Redirect to the personal workspace with the message: Invalid link. 2. null |
|
| 65 | Repository settings/Repository member management | Invite users as developers through invitation link in repository member management (without audit enabled): Correct invitation link | Functional testing | P1 | 1. Warehouse administrator Bob logged in status 2. Bob enters the repository member management page. 3. Role permissions default to Developer |
1. Bob clicks "Copy Link" to send the invitation code to Bob, who is outside the repository 2. Bob gets the invitation code and enters the correct invitation code in the browser: https://gitee.ru/Alice/test-repo/invite_link?invite=XXX |
1. The confirmation box correctly displays "Alice (inviter) invites you to join the repository as a developer" 2. Repository ownership and name are displayed correctly, shown as Bob/test-repo 3. Repository Introduction is displayed correctly 4. Join successfully |
|
| 66 | Repository settings/Repository member management | Repository member management - Add repository members via link | Functional testing | P1 | 1. User is logged in 2. Go to the repository member management under the repository management page |
Add repository members, invite users Choose invitation link, set repository permissions, select administrator approval required, copy the address, and send it to the user User access link, accept invitation, administrator confirms |
Jump to invitation method page This invitation link requires administrator approval to join Join successful |
Assign x celebrities to review or test, choosing a minimum number of people from 0 to x |