HOME > Community > Projects > qa

NetBeans Subversion Support Test Specification

Author: Peter Pis
Version: 1.0.0
Last update: 22.03.2006
Introduction: Subversion open source tool is one of the supported version control systems in the IDE. This document describes how SVN profile for NetBeans SVN Support module should be tested in order to know whether all of its functionality work correctly. All Test Suites should be performed with all access method types: "file:///", "svn://", "svn+ssh://", "http://" and "https://"
Comment:

1. Setting up URL
2. Importing new project
3. Standard development of project
4. Working with Copies/Branches
5. Archeology

Test suite 1: Setting up URL

Purpose: This suite tests whether it is possible to access valid Subversion repository using different types of connections.
Setup: Subversion command-line client version 1.3 or higher has to installed on tested platform.

# Test case Description

svn://

Invoke Subversion | Checkout... action from main menu. "Checkout" wizard shows up.
Switch to Repository URL field and set it to e.g. "svn://localhost/svn"
After setting up "svn://" connection type there should be visible "User", "Password" and "Proxy Configuration..." components.
Setup username and password and verify functionality of "Proxy Configuration" dialog.

RESULT: Push Next button. Next dialog of "Checkout" wizard should show up. Verify that "Browse..." buttons are show for "Repository Folder(s)", "Local Folder" and "Search" button for "Repository Revision" in this step of "Checkout" dialog. Push "Finish" button. Verify result of Checkout action.

svn+ssh://

Setup: In case of windows platform "plink" application should have been installed.

Invoke Subversion | Checkout... action from main menu. "Checkout" wizard shows up.
Switch to Repository URL field and set it to e.g. "svn+ssh://localhost/svn"
After setting up "svn+ssh://" connection type there should be visible "User", "Password" and "Proxy Configuration..." components.
Setup valid password.

RESULT: Push Next button. Next dialog of "Checkout" wizard should show up. Verify that "Browse" buttons are show for "Repository Folder(s)", "Local Folder", "Repository Revision" and "Search" button in this step of "Checkout" dialog. Push "Finish" button. Verify result of Checkout action.

file:///

Invoke Subversion | Checkout... action from main menu. "Checkout" wizard shows up.
Switch to Repository URL field and set it to e.g. "file:///svnrepo"

http://

Invoke Subversion | Checkout... action from main menu. "Checkout" wizard shows up.
Switch to Repository URL field and set it to e.g. "http://localhost/svnrepo"
After setting up "http://" connection type there should be visible "User", "Password" and "Proxy Configuration..." components.
Setup valid password.

https://

Invoke Subversion | Checkout... action from main menu. "Checkout" wizard shows up.
Switch to Repository URL field and set it to e.g. "https://localhost/svnrepo"
After setting up "https://" connection type there should be visible "User", "Password" and "Proxy Configuration..." components.
Setup valid password.

RESULT: Push Next button. You will be asked for accept the certificate. Next dialog of "Checkout" wizard should show up. Verify that "Browse" buttons are show for "Repository Folder(s)", "Local Folder", "Repository Revision" and "Search" button in this step of "Checkout" dialog. Push "Finish" button. Verify result of Checkout action.

Test suite 2: Importing new project

Purpose: The goal of this suite is to create new project and upload it to Subversion repository.
Setup: No setup is necessary.

# Test case Description

Project import

Invoke File | New Project... from main menu.
"New Project" wizard shows up. Choose e.g "General | Java Application" and push "Next" button.
Setup name of the project, project location as desired and push "Finish" button.
Switch to "Projects" view and select the root of the project.
Invoke Subversion | Import into Repository... from main menu.
"Import" wizard shows up.
Setup "Repository URL" as desired and all necessary fields for chosen access method and push "Next" button. All displayed components depend on access method type - see "Setting up URL".
Push Browse... button. Verify that browsing through the repository is allowed. Verify also functionality of New Folder (it creates only virtual folders. Nothing is changed in the repository.)
Enter some comment into "Import Message" field and push "Next" button. All displayed components depend on access method type - see "Setting up URL".
3rd step of Import wizard shows up. Verify whether you can change values in "Commit Action" column. (Add As Text, Add As Binary and Exclude From Commit).

RESULT: In "Output" tab verify whether "Import" and "Check out" command finished successfully. Now context commands on this project root in "Projects" view shouldn't contain "Import into Repository" action. All sources should be imported and subversion actions should be available.

Test suite 3: Standard development of project

Purpose: This suite tests the most often used commands of typical Subversion user.
Setup: No setup is necessary except steps from previous test suite.

# Test case Description

Update action

Switch to "Files" view.
Invoke Subversion | Update popup menu action on project root.

RESULT: Verify that in "Output" tab there is message " ==IDE== date time Updating "Project" finished.".

File modifying

Select e.g. "Main.java" file, modify it.
Insert brand-new line somewhere into the file.
Delete some other line but not directly next to the new line.
Modify another line but not directly next to the lines mentioned above and Save the file.

RESULT: The file "Main.java" must change its foreground color to blue.

File differences

Select this file.
Invoke Subversion | Diff "Main.java" action from main menu.

RESULT:

All three differences must be highlighted in a special window with both versions of the file. New line is green, removed line is red and modified one is blue. At the bottom of this component there is part for viewing properties differences.

Files/Folders differences

Create new package "xx.yy" in this project.
Create new "java class" "NewClass" in package "xx.yy".
Invoke Subversion | Show "Project" Changes from main menu.
Files should be listed in "Subversion" tab - "Main.java" and "NewClass". Also the new packages "xx.yy"should be displayed as [New].
Select the root of the project and invoke Subversion | Diff popup menu action.

RESULT: Special window is displayed. "Main.java, NewClass.java, xx, yy" should be contained in combobox field. Verify functionality of "UP" and "DOWN" arrows. (Arrow navigates among all differences on processed files). Verify functionality of "Diff" icon in "Subversion" tab - same result as for context command. "Diff all" component provides icons for "Refresh Status", "Update all" and "Commit all" action.

Commit files/folders

Switch to "Subversion" tab.
Push "Commit all" icon.
"Commit dialog" shows up. It should contain two files: "Main.java", "NewClass.java", and two folders "xx" and "yy". Enter some commit message and push "Commit" button.

RESULT: Verify that blue badges disappeared. Files and folders/packages should disappear from "Subversion" tab immediately too.

Creation of patch

Modify "Main.java" file and save it.
Modify "NewClass.java" file and save it.
Select project root and invoke Subversion | Export "Project" Diff Patch... from main menu. Select desired output file for patch and confirm the dialog.

RESULT:

Patch should be created in your chosen file. If this action is invoked on context that has no modified files, information dialog should be displayed only.

WILL BE IMPLEMENTED LATER

Applying patch

Switch to "Files" view and select project root.
Invoke Subversion | Revert Modifications from main menu or popup menu. (Select "Revert Local Changes" option and push Revert button.)
Make sure that all modified files are "uptodated" now.
Select project root and invoke Tools | Apply Diff Patch... popup menu action.
Answer "Yes" in question dialog to confirm watching differences.

RESULT: Verify that new tabs were opened into the editor for all patched files. Verify results generated by "Command-line Diff" and "Built-in Diff" engines. Verify results displayed by "Graphical Diff Viewer" and "Textual Diff Viewer" visualizers.

TBD

Create conflict

Modify "Main.java" file and save it.
Invoke Subversion | Check out... from main menu and setup the same parameters as for previous Suites but with different "Workfile location".
Open the same project, modify "Main.java" class at the same line as in previous test suite, and commit it.
Return to previous project, select the project root and invoke Subversion | Update with Dependencies popup menu action.

RESULT: "Conflicts warning" dialog should be displayed. Path to "Main.java" file should be indicated with red badges. This file should change its color to red too. Verify functionality of All, Local and Remote buttons in "Subversion" tab.

Resolve conflict

Invoke Subversion | Resolve conflicts popup menu action on "Main.java" node.
Merging tool must get opened in editor area highlighting the line with conflict. Left pane should read "Working File", right pane "Remote File" and bottom should read "Merge Result".
Select left modification (the working one) and push "Accept" button above its pane.
Make sure that colors changed to blue or green and "Unresolved" in top of the component says "0 conflicts". Push "OK" button and confirm your decision.

RESULT: The data node should change back to "Main.java" and should have appropriate badge (blue badges for path). In addition, the merge tool must be closed.

Delete file

Switch to "Projects" view and expand "xx.yy" package node.
Invoke Delete popup menu action on "NewClass.java" file node.
Confirm your decision by clicking Yes in follow-up question dialog.
File should disappear from all explorer views. It should appear in "Subversion" tab with "Locally Deleted" status.
Select "NewClass.java" in "Subversion" tab and invoke Revert Delete action
Confirm your decision by clicking Yes in follow-up question dialog.
File should appear in all of explorer views.
Invoke Delete popup menu action on "NewClass.java" file node again.
Confirm your decision by clicking Yes in follow-up question dialog.
Select "NewClass.java" in "Subversion" tab and invoke Commit...
"Commit" dialog shows up. Fill commit message and push "Commit".

RESULT: File "NewClass.java" should disappear from all explorer views, and from "Subversion" tab.

Delete Folder(s)

Select package node that contains files.
Invoke Delete popup menu action on package node.
Confirm your decision by clicking Yes in follow-up question dialog.
Select all deleted nodes in "Subversion" tab and invoke Revert Delete
Confirm your decision by clicking Yes in follow-up question dialog.
Package and its files should appear in all of explorer views.
Repeat 2nd step.
Confirm your decision by clicking Yes in follow-up question dialog.
From "Subversion" push Commit button.

RESULT:

Package with its content should disappear from all views.

TBD

Project Deletion

Create new project.
Add this project into the source control. Invoke Subversion | Show All Changes from main menu.
Switch to "Projects" view, select project node and invoke Delete Project popup menu action. (Confirm dialog and delete also sources)

RESULT: All files should appear in "Subversion" view. These files should be in "Locally Deleted" status. Select all files in "Locally Deleted" state and invoke Revert Delete popup action from "Subversion" view. After successful action it should be allowed to open this project again.

TBD

Exclude file from commit

Create "JFrame" in "xx.yy" package.
Invoke Subversion | Commit... on this JFrame in "Projects" view.
Switch to "Subversion" tab, there should be listed "NewJFrame.java" and "NewJFrame.form" files. Select both the files and invoke Commit....
"Commit" dialog should be displayed with these JFrame files. Change the "Commit Action" to "Exclude from Commit" for both files. Push "Commit" button.

RESULT: Both files have to be excluded from commit with no change of their statuses. Include in Commit action should be accessible in popup menu actions in "Subversion" tab and performing Include in Commit must return file to "committing" status.

Ignore file

Create new "Java class" ("NewClass2") into "xx.yy" package.
Select this java file and invoke Subversion | Ignore .

RESULT: "NewClass2.java" should change its color to gray with [Ignored] annotations in all explorer views and it should disappear from "Subversion" tab.

Ignore folders

Create new "New Package" ("tt2") into "javaapplication" package.
Select this "tt2" package and invoke Subversion | Ignore .

RESULT: "tt2" should disappear from "Subversion" view. Externally verify that ".svn" administrative directory of parent folder of "tt2" package contains file "dir-props" listing "tt2" package.

Unignore file

Select "NewClass2.java" in "Projects" view and invoke Subversion | Unignore popup menu action.
"Subversion" tab should contain "NewClass2.java (Locally New)" files. Path to this should be indicated with blue badges.
Select project root and invoke Subversion | Commit All Files action from main menu.
"Commit" dialog shows up, enter some commit message and push "Commit" button.

RESULT: File should disappear from "Subversion" tab. Font color of "NewClass2.java" file is black now. Externally verify that ".svn" administrative directory of parent folder of "NewClass2.java" package doesn't contain this file listed in "dir-props".

Reverting modifications

Open "NewClass2.java" to editor.
Insert brand-new line somewhere into the file.
Delete some other line but not directly next to the new line.
Modify another line but not directly next to the lines mentioned above and Save the file. File name color should change to blue, verify the path indicating blue badges.
Select "NewClass2.java" and invoke Subversion | Revert Modifications
"Revert Modifications" dialog should show up. There are three choices: "Revert Local Changes", "Revert Modifications from Single Commit" and "Revert Modifications from Previous Commits". "Revision" should be enabled for second choice. "Starting Revision" and "Ending Revision" revision should be enabled for third choice only. This dialog provide also the functionality of rollbacking changes. For each of these fields "Search..." button should be available.

RESULT: All changes should be reverted. Indicating badges should disappear. "NewClass2.java" file should not be listed in "Subversion" tab.

Global actions

Invoke Show All Changes action from main menu.
Invoke Diff All Files action from main menu.
Invoke Update All Files action from main menu.
Invoke Commit All Files action from main menu.

RESULT:

Verify functionality of all above mentioned commands.

Actions in Projects view

Add new package "aa" and new "Interface.java"
Add new package "aa.bb" and new "NewClass.java"
Invoke Subversion | Commit... on "aa" package.
Commit dialog shows up. There should be "Interface.java" and "aa" listed in commit dialog. Push "Commit" button.
Make sure that only "aa" and its file were added. Have a look in tab for SVN URL in "Output" window.

RESULT: Subversion actions invoked on packages "Projects" view shouldn't be performed recursively. Make sure that Update, Diff, Switch to Branch, Merge Changes From Branch, Export Diff Patch and Revert Modifications work correctly. In case of branching actions verify whether new files and folders are added/removed properly.

Refactoring

Select "Main.java" node and invoke Refactor | Rename... popup menu action on it.
Enter new name for it and push "Next" button. Special window shows up, push Do Refactoring.
File with new name should be listed in "Subversion" view as "[Locally Renamed]" and old one "[Locally Deleted]".
Commit both files and verify whether new file inherited history by refactoring.
Switch to "Files" view, select package "xx" and invoke Refactor | Rename... popup menu action on it.
Enter new name "yy" for it and push "Next" button. Special window shows up, push "Do Refactoring".
Make sure that all refactored nodes with new name are marked as "[Locally Copied]" (for directories only "[New]" is shown) in the "Subversion" tab. "yy" is "[New]", "NewClass" and "Main" from "yy" are "[Locally Copied]]". "NewClass" and "Main" from "xx" are "[Locally Deleted]]".

RESULT:

Push Commit make sure that file nodes disappear. And all files/directories were committed as well.

Test suite 4: Working with Copies/Branches

Purpose: This suite tests work-flow with copies/branches.
Setup: No setup is necessary except steps from previous test suite.

# Test case Description

Copy/Branch creation

Select project root and invoke Subversion | Copy to... popup menu action.
Dialog for branching shows up. Setup "Copy to Repository Folder" (create new location for copy purpose). Push Browse button. Verify functionality of this component. Try to create new folder with use of New Folder button or through the popup menu on some node in "Repository Browser" component.
Enter "Copy Description" field.
Verify that "Switch to Copy" check box is displayed in dialog and check it.
If this action was invoked on context with some modified files make sure that warning message is being displayed about locally modified files in context.

RESULT: Verify in "Output" tab whether project was branched properly. Nodes in explorer view should be annotated. If "Switch to Copy" was not checked, then sources shouldn't be switched to new created copy.

Committing to branch

Select the "Main.java" file, modify and save it.
Invoke Subversion | Commit... popup menu action.
Commit dialog shows up and there should be listed "Main.java" file and information about the commit - "Committing to "Project" branch". Push "Commit" button.

RESULT: Verify in "Output" tab whether the action finished successfully.

Multiple branches

Create new e.g. "NewInterface" in this project.
Select project root and invoke Subversion | Commit... project from popup menu.
Commit dialog shows up and there should be listed "NewInterface.java" file and information about the commit - "Committing to "Project" branch". Push the Commit button.
Verify successful commit of new added file.
Now select project root and invoke Subversion | Switch to Copy... popup menu action.
Appropriate dialog shows up. Browse desired "Repository Folder" and desired "Revision" where "NewInterface" doesn't exist.
"NewInterface" file should disappear from all views.
Select again project root and invoke Subversion | Switch to Copy... popup menu action.
Verify that "Repository File (Folder)" (depends on context it was invoked for) combo box, "Browse" button, "Repository Revision" text field and "Search" button were shown.
Choose "Repository File/Folder", desired revision number and push Switch button.
Verify whether "NewInterface" file appears in all views again.
Select "Main.java" file and invoke Subversion | Switch to Copy... popup menu action.
In the dialog setup "Repository File/Folder" for trunk and push the Switch button.
Verify that file contains changes made in the trunk.
Modify and save both "Main.java" and "NewInterface" file.
Select the project root and invoke Subversion | Commit "Project"... from the main menu.
Dialog shows up, with these two files. There should be warning about attempt to commit to multiple branches - commit dialog now contains also "Branch" column - if there is nothing in the column, the file is to be commited to the trunk, otherwise to some branch (its name will be there).

RESULT: Verify that "Main.java" was committed to trunk and "NewInterface" was committed to "Copy" location. (Switch to both locations and verify changes.)

Merge from branches

Select the project root, invoke Subversion | Switch to Copy... action.
In the dialog setup "Repository File/Folder" for trunk and push Switch button.
All project sources should contain only "Trunk" changes.
Create "NewInterface" and add new method to "NewInterface", save and commit it.
Add new variable to "Main.java", save and commit it.
Switch project to "new_copy".
Open "Main.java" into the editor, modify the type of the variable created in step 5 at the same line. Save the file.
Open "NewInterface" into the editor, modify the return value of the method created in step 4 at the same line. Save the file.
Select project root invoke Subversion | Merge ... popup menu action.
Dialog shows up. There are three choices for merging. Each of choice has descriptive picture. Verify all their components and functionality for each case. Push Merge button.
Dialog shows up with the information that there were conflicts.

RESULT: Files in conflicts are displayed with red color in "Subversion" tab. Resolve all the conflicts.

Test suite 5: Archeology

Purpose: This suite tests "archeology" searching with various criteria.
Setup: No setup is necessary except steps from previous test suite.

# Test case Description

Search button

Invoke Subversion | Checkout... wizard from main menu.
Setup valid "Repository URL" and proceed to 2nd step of "Checkout" wizard.
Push Search... button.
"Search Revisions" dialog shows up.
"List Log Entries from" field and "List" button should be there. Push the "List" button.
There should be listed records containing "Repository Revision Number", "User Name", "date and time" and "Commit Message" for each record in it.
Select some record and push OK button.

RESULT: Verify that "Search Revisions" dialog was closed and "Repository Revision Number" was setup into "Revision:" field of "Checkout" wizard. This component is also accessible from "Switch Copy to", "Merge ...", "Revert Modifications" dialog. Verify them too.

Annotations

Select "Main.java" node and invoke Subversion | Show Annotations popup menu action.
"Annotations" column and "Stripes" should be displayed around the editor area of this file.
Select desired line (with revision e.g. "12").
All lines with revision ("12") should be colored blue in "annotations" column. "Stripes" should show navigations to this revision too.
Move mouse pointer over "Revision" column and invoke popup menu.

RESULT:

There should be Diff 12 to 11, Revert Modifications... and Close Annotations actions listed in popup menu.

Annotations actions

Choose Diff... action.
"Diff" tab should be opened into the editor for specified revisions.
Choose Revert Modifications... action.
This action should show "Revert Modifications" dialog. (See "Standard Workflow" test suite - "Revert modifications")
Choose Close Annotations action.
This action should hide annotation column and stripes too.

RESULT:

Verify functionality on various revisions and navigations with the use of "Stripes".

Search history

Switch to "Projects" view and select project root.
Invoke Subversion | Search History... popup menu action.

RESULT: "Search History" tab for this project should be displayed in editor area. Verify also functionality of "Browse" buttons next to "From" and "To" fields.

Summary functionality

Make sure that "Summary" toggle button is pushed.
Push Search button.

RESULT: Verify that all files of the project are listed in "Summary" output area. All items there should contain "revision number", "username", "date", "file location", "file name", "commit message" and "Diff" and "Revert" link there.

Summary actions

Invoke popup menu on desired record in "Summary" section.
There should be Diff to Previous Revision and Rollack Changes.

RESULT:

Verify the functionality of each action. Behavior of these actions was described in Annotation actions section. Rollback Changes action can be invoked on multi selection that will rollback all differences among selected revisions.

Diff functionality

Select project root and invoke Subversion | Show History... popup menu action.
Push Search button and then click "Diff" toggle button.

RESULT: Verify that table with list of files is displayed. Also area for "Diff" should be there.

Diff actions

Invoke popup menu on desired revision of the file in "Diff" section.
There should be Rollback Changes action listed in popup menu.

RESULT:

Exploring revisions

Select some file in this table that has more revisions and expand node.
Select some revision.

RESULT: In "Diff" output area there should be displayed differences between selected and previous revision. On multi selection of two revisions of the same file there should be displayed differences between them. Differences should not be displayed for different files.

Random search

Invoke Subversion | Search History... on file, projects.

RESULT: Verify the functionality of "Search History" action on files, packages and project nodes. Verify that searched results meet searching criteria.

Generated: 2006 12 07 04:15