8/17/2004 6:17:27 PM

Testcase Breakout for GridView

Hierarchy: All Testcases -> Web.NET -> Page & Controls -> Controls

GridView

Area

Test Plan for the GridView control.

Review History

Oct 7, Started test plan
Oct 11, Test Plan review
Oct 16, Finished adding changes to the Run time area of test plan
Feb 21, Testplan consitency push. Added areas for accessibility , user controls, extensibility, stress and themes.
Apr 29, General Resync to spec. Added properties that were missing and miscelaneous tests

Dialogs

< a>farmas

DataBinding - Test the DataBiniding dialog

Pri 3, Coding

Abstract:
This test will only verify the basic functionality of the databinding dialog works for this controls. Additional and more extensive tests will be done in the DataBinding Area

- Verify the DataBinding dialog can be opened
- Verify basic functionality works (title contains the name of the control, the correct properties are shown on the list, etc)

(This testcase is to be modified to check the data binding dialog for the controls inside GridView/DetailsView/FormView's templates)

(Note by yihuax: LanO probably has the coverage of this one)

Scenarios:
1) Open the DataBinding dialog
2) Verify the ID of the control appears in the title
3) Verify the list of databindable properties is complete
4) Data bind a few properties to the page and other to custom expressions
5) Verify the datacan icon appears on the databound properties
6) Close the dialog, verify the databound properties show the datacan icon in the property grid
7) Verify persistence of the databound properties

ImageUrlEditor - Test the ImageUrlEditor dialog to input the ImageUrl properties

Pri 3, Coding

Abstract:
This test will not check in depth the functionality of the ImageUrlEditor dialog.

Repeat this test for the following properties:
- BackImageUrl
- BoundField.HeaderImageUrl
- CheckBoxField.HeaderImageUrl
- ImageField.HeaderImageUrl
- ImageField.NullImageUrl
- ButtonField.HeaderImageUrl
- CommandField.HeaderImageUrl
- HyperlinkField.HeaderImageUrl
- HyperlinkField.NavigateUrl
- (When choosing EditField.ButtonType=Image)
- (When choosing ButtonField.ButtonType=Image)

Scenarios:
1) Verify that the "..." button appears next to the property
2) Verify that the ImageUrlEditor dialog appears when the "..." button is pressed.
3) Verify the title of the dialog
4) Verify that the basic functionality works (buttons, browsing, relative & absolute path)
5) Verify the default settings of the dialog are correct (starting folder, type of path, selected Url)
6) Input a valid Url
7) Close the dialog and verify the persistence of the entered Url
8) Reopen the dialog and verify the Url is still there as well as the file selected in the treeview (if applicable)

Add Field

< a>farmas

AddField_Bound1 - Test the layout of dialog when adding a BoundField

Pri 2, Coding

1) Add a GridView
2) Click on Add Field button in chrome
3) Select BoundField
4) Verify no dropdown is schema aware
5) Verify the layout of the dialog
6) Fill all textboxes
7) Add a BoundField and verify persistence
8) Bind the grid to a datasource
9) Open dialog and verify BoundField's template is schema aware
10) Without filling anything add the field
11) Verify persistence
12) Open dialog and verify BoundField's template is schema aware
13) Use the dropdownlist to fill the data
14) Add a BoundField and verify persistence

AddField_Button1 - Test the layout of dialog when adding a ButtonField

Pri 2, Coding

1) Add a GridView
2) Click on Add Field button in chrome
3) Select ButtonField
4) Verify the layout of the dialog
5) Verify the items displayed in the CommandName dropdown are correct
6) Verify ButtonType is Link and Button
7) Choose a different command name from the list
8) Add the ButtonField and verify persistence
9) Open dialog again
10) Fill all textboxes, choose Link as the Button type
11) Type a command name into the combobox
12) Add the ButtonField and verify persistence

AddField_CheckBox1 - Test the layout of dialog when adding a CheckBoxField

Pri 2, Coding

1) Add a GridView
2) Click on Add Field button in chrome
3) Select CheckBoxField
4) Verify the layout of the dialog
5) Verify no dropdown is schema aware
6) Fill all textboxes
7) Add a CheckBoxField and verify persistence
8) Bind the grid to a datasource
9) Open dialog and verify ChecBoxField's template is schema aware
10) Verify dropdown only contains columns that are of type bit/bool
11) Without filling anything add the field
12) Verify persistence
13) Open dialog and verify BoundField's template is schema aware
14) Fill all data
15) Add a CheckBoxField and verify persistence

AddField_CheckBox2 - Verify the bug 83023 & 141937

Pri 1, Pending Code Review

Abstract:
83023 GridView: Add New Column dialog lets you add columns for invalid data types

141937 Exception thrown when attempting to add a CheckBoxField and the bound table contains no column of boolean type

Scenarios:
1) Add a GridView and an associated SqlDataSource to a page
2) Set the SqlDataSource to connect to a table that has columns other than bit/bool (pretty much any table)
3) Use the GridView's Add New Column verb to add a new column
4) Select CheckboxField
5) Verify that the datafield dropdown contains no items
6) Click the OK button
7) Verify no error

AddField_Command1 - Test the dialog when adding a CommandField

Pri 3, Coding

Abstract:
[06/30/2003 farmas] it is still unclear how the checkboxes will work for this dialog. Revisit scenarios once it is defined

Scenarios:
1) Add a GridView
2) Click on Add Field button in chrome
3) Select CommandField
4) Verify the layout of the dialog
5) Verify all elements in dialog are present and with correct status (enabled/disabled/checked)
6) Verify the texts are all localized.
7) Add a CommandField and verify persistence

AddField_Hyperlink1 - Test the layout of dialog when adding a HyperlinkField

Pri 2, Coding

1) Add a GridView
2) Click on Add Field button in chrome
3) Select HyperlinkField
4) Verify no dropdown is schema aware
5) Verify the layout of the dialog
6) Fill all textboxes
7) Add the field and verify persistence
8) Bind the grid to a datasource
9) Open dialog and verify HyperlinkField's template is schema aware
10) Without filling anything add the field
11) Verify persistence
12) Open dialog and verify HyperlinkField's template is schema aware
13) Use the dropdownlist to fill the data
14) Add the field and verify persistence

AddField_Image1 - Test the use of AddField dialog to add image fields

Pri 1, Complete

Abstract:
<asp:imagefield Mode="ImageData" DataField="image_column" AlternateText="ThePhoto" NullImageUrl="Empty.jpg"/>
<asp:imagefield Mode="ImageURL" DataField="image_column" AlternateTextField="name"
AlternateTextFormatString="{0}'s photo" NullDisplayText="No Photo"
ImageUrlFormatString="image/photo_{0}.jpg" />

Add a GridView
Click on Add Field button in chrome
Select ImageField
Fill all textboxes according to the first tag above.
Add the field
Open dialog again
Use the dropdownlist to fill the data
Fill all properties according to the second tag above.
Add the field
Verify the two image fields in the Field Edit dialog.
Verify the two tags in html view.

Scenarios:
1) Add an AccessDataSource in the design surface and set the data file
2) Set SelectCommand and refresh schema
3) Add a GridView control in the design surface
4) Bind GridView to the DataSource
5) Invoke the Add Field dialog
6) Add an image field
7) Invoke the Add Field dialog again
8) Add an image field
9) Invoke the Field Editor dialog
10) Verify the Image Field are shown in the editor
11) Select the Image Field added already
12) Verify the Image Field's property
13) Define the Image Field's property
14) Verify the first Image Field in html view
15) Verify the second Image Field in html view

AddField_Schema1 - Test the Refresh schema link of the dialog and grid does not has schema

Pri 2, Coding

1) Add a GridView control
2) Bind it to a datasource
3) Open the dialog
4) Fill all the texts of Bound Field with some strings
5) Click on the refresh schema link
6) Verify schema dialog is opened
7) Click on FINISH on the dialog
8) Verify dropdownlist is populated with values from source, and nothing is selected
9) Verify the static textboxes retained their values
10) Cycle to all templates and verify the dropdown lists are correct

AddField_Schema2 - Test the Refresh schema link of the dialog and grid already has schema

Pri 2, Coding

1) Add a GridView control
2) Bind it to a datasource and refresh the schema
3) Open the dialog
4) Fill all the texts of Bound Field with some strings
5) Click on the refresh schema link
6) Verify schema dialog is opened
7) Click on FINISH on the dialog
8) Verify dropdownlist is populated with values from source, and nothing is selected
9) Verify the static textboxes retained their values
10) Cycle to all templates and verify the dropdown lists are correct

AddField_Template1 - Test the layout of dialog when adding a TemplateField

Pri 2, Coding

1) Add a GridView
2) Click on Add Field button in chrome
3) Select TemplateField
4) Verify the layout of the dialog
5) Add the field and verify persistence
6) Reopen dialog
7) Type something in the header text
8) Add the field and verify persistence

AddField2 - Test the invocation of dialog under different circumstances

Pri 1, Coding

Abstract:
[06/30/2003 farmas] After user opens dialog, do a basic sanity check of all templates of dialog (just check that one control of the dialog is there)

[06/30/2003 farmas] Check if the dialog will be able to load custom fieldtypes

Scenarios:
1) Add a GridView
2) Invoke the dialog
3) Verify dropdwon contains all fieldtypes
4) Verify default view of dialog (BoundField)
5) Verify schema link is disabled
6) Bind the grid to a schema-less datasource control
7) Invoke the dialog
8) Verify default view of dialog (BoundField)
9) Verify schema link is enabled
10) Bind the grid to a schema aware datasource control
11) Invoke the dialog
12) Verify default view of dialog (BoundField)
13) Verify schema link is enabled
14) Add all fields as bound fields
15) Select the a column
16) Invoke the dialog
17) Verify default view of dialog (BoundField)
18) Verify schema link is enabled

AddField3 - Tests the position of the created column

Pri 2, Coding

1) Add a Grid
2) Bind to a schema aware datasource
3) Open the dialog and add a Field
4) Verify column appears at the left side and is selected
5) Open the dialog and add a Field
6) Verify column appears at the second position and is selected
7) Set AutoGenerateColumns to false
8) Select the last column
9) Open the dialog and add a Field
10) Verify column appears at the right and is selected
11) Select the middle column
12) Open the dialog and add a Field
13) Verify column appears at the 3rd position and is selected
14) Verify persistence

AddFieldSanity - Verify dialog appears and is operational

Pri 1, Complete

1) Click on Add Field button in chrome
2) Add a Bound Field
3) Verify design time renderig and aspx persistence

AutoFormat

< a>farmas

AutoFormatApply - Apply button

Pri 1, Coding

Abstract:
110263 AutoFormat dialog - pressing Apply should disable after applying

Scenarios:
1) Add the control
2) Bring up the autoformat dialog
3) Verify all controls are visible
4) Choose an item from the list and click Apply
5) Verify in the background that the datagrid updates to the selected scheme
6) Verify Apply button is disabled
7) Click Cancel
8) Verify properties were changed on the control

AutoFormatCancel - Test the cancel button of the autoformat dialog

Pri 3, Coding

1) Add the control
2) Bring up the autoformat dialog
3) Verify all controls are visible
4) Choose an item from the list
5) Choose Cancel
6) Make sure no properties were changed on the control

AutoFormatFunctionality - Test the loading of properties from the Auto Format and persistence

Pri 1, Coding

Abstract:

Each time the scheme is changed verify that properties that are not scheme-bounded persist (i.e. the texts of the labels)

Scenarios:
1) Add GridView.
2) Define a few column fields.
3) Open the Auto Format dialog
4) Verify that the preview pane updates depending on the selected scheme
5) Verify that the controls in the preview pane are disabled
6) Choose a scheme
7) Verify the correct properties get loaded in the control
8) Verify persistence in html and design view
9) Reopen and verify selected scheme and preview
10) Remove Auto Format
11) Verify properties switch back to default in html and design view
12) Verify the columns fields still exist.

AutoFormatHelp - Test the help button and screen of the Auto Format Dialog

Pri 3, Coding

1) Add a Gridview Control
2) Click on the "Auto Format ..." link
3) Click on the Help button
4) Verify button is working
5) Verify the help page that appears for correctness

AutoFormatList - List of schemes

Pri 3, Coding

1) Add the control
2) Bring up the autoformat dialog
3) Verify the items in the list are the same as expected

GridView_AFDialogOk - Simple sanity check for OK button of Auto Format dialog

Pri 1, Complete

Abstract:
Used for the nightly
Basic sanity test
Just select one scheme and verify one property

Scenarios:
1) Invoke the AutoFormat dialog
2) Select the desired scheme
3) Click OK to close the dialog
4) Verify that the scheme got applied
5) Build and Run

ResetFormatting - Test the resetting functionality of the AutoFormat dialog

Pri 1, Coding

Abstract:
140701 GridView persists unneeded style elements after un-format

Scenarios:
1) Add a GridView control
2) Open the autoformat dialog
3) Select a scheme and click OK
4) Verify styles are present
5) Open the autoformat dialog
6) Select Reset Formating and click OK
7) Verify styles are gone
8) Open the autoformat dialog
9) Select a scheme and click apply
10) Select ResetFormating and click Apply
11) Click OK
12) Verify no styles are added
13) Open the autoformat dialog
14) Select a scheme and click apply
15) Select ResetFormating and click Cancel
16) Verify styles are added.

ScottGu Note: Several hundred pages after this omitted….