Compartilhar via

Test Area 4: Check In

  • Artigo

This source-control plug-in test area covers sending updated items to the version store via the Check In command.

Command Menu Access

The following Visual Studio integrated development environment menu paths are used in the test cases.

Check In:

File, Source Control, Check In.

File, Check In.

Shortcut menu, Check In.

Common Expected Behavior

  • Projects and files added to a solution or project under source control appear in the Check In dialog box and the Pending Checkins window.

  • After the check in, added items appear in source control.

  • After the check in, updated items are properly versioned in the store.

Test Cases

The following are specific test cases for the Checkin test area.

Case 4a: Modified items

Describes using the check in action to update a file under source control that has been modified.

Action

Test Steps

Expected Results to Verify

Modify a text file that has been checked out, check in file only (Check In dialog box)

  1. Create a new project with a text file.

  2. Add the solution to source control.

  3. Check out and modify the text file.

  4. Check in via the Check In dialog box (File, Source Control, Check In).

Common Expected Behavior.

Modify a text file that has been checked out, Check in file only (Pending Checkins window)

  1. Create a new project with a text file.

  2. Add the solution to source control.

  3. Check out and modify the text file.

  4. Check in via the Pending Checkins window.

Common Expected Behavior.

Case 4b: Adding files

When adding a file to a project or an item to a solution, the project or solution must change also. Thus the parent file is also checked out and must be checked in to complete the addition.

Action

Test Steps

Expected Results to Verify

Add a text file and check in everything (Check In dialog box)

  1. Create a new project.

  2. Add the solution to source control.

  3. Add a text file to the project.

  4. Accept check out of the project if prompted.

  5. Select the solution in Solution Explorer.

  6. Check in from the Check In dialog box.

Common Expected Behavior.

Add a text file and check in everything (Pending Checkins window)

  1. Create a new project.

  2. Add the solution to source control.

  3. Add a text file to the project.

  4. Accept check out of the project if prompted.

  5. Check in solution from Pending Checkins window.

Common Expected Behavior

Case 4c: Adding projects

When adding a project to a solution, the solution must change also. Thus the solution file is also checked out and must be checked in to complete the addition.

Action

Test Steps

Expected Results to Verify

Add a project to a blank solution under source control (Check In dialog box)

  1. Create a blank solution.

  2. Add the solution to source control.

  3. Add a new project.

  4. Accept check out of the solution if prompted.

  5. Check in from the Check In dialog box.

Common Expected Behavior.

Add a project to a blank solution under source control (Pending Checkins window)

  1. Create a blank solution.

  2. Add the solution to source control.

  3. Add a new project.

  4. Accept check out of the solution if prompted.

  5. Check in solution from Pending Checkins window.

Common Expected Behavior.

See Also

Concepts

Test Guide for Source Control Plug-ins