Testplan Checklist for Asp.Net
a.k.a. The “I didn’t know I had to test that” checklist.
Each tester is responsible for ensuring that his/her feature integrates correctly with the rest of Asp.Net, which is a challenge because Asp.Net is a very big product and almost no one can keep all the different features in their head. To address this, our team maintains a "checklist" of integration points that each tester must investigate while creating his/her testplan. Each item links to a page with more information and resource links (which I omit here due to space), and the idea is for the tester to do research on each area and discuss with their feature crew if any interesting tests can be done with each point.
Federico Silva Armas
Asp.Net QA Team
Areas that are interesting to both controls and runtime features: - Output Caching(Page & User Control)
- Trust levels
- Async pages
- Precompilation
- NoCompile pages
- Virtual Path Provider
- Debugging
- Languages: VB and C#
- Impersonation
- Perf counters
- Browser dependencies
- Custom errors
Areas that are interesting for controls: - Themes – is control themable?
- UserControl – how does the control work inside the user control?
- Master Pages – does control work inside a master page?
- Viewstate on/off
- Encryption of ViewState
- Adaptive Rendering
- Cross-page posting
- Callbacks
- Behaviour inside an Update panel
- Behaviour inside MVC web site
- Behaviour inside WebPart
- XHTML conformance
- Use Standard tests - automated test that verifies property values for controls
- Tracing
Areas that are interesting for runtime: - Custom errors
- Cassini Web Server
- Domain Controllers
- Http Intrinsics
- Page lifecycle
- Process identity
- Process model, including differences b/w IIS7 classic and integrated mode
- Time Zones
- UNC
Areas that are interesting for script-based (Ajax) features: - Debug/release
- Different browsers
Designer considerations
These scenarios are only interesting if your feature has a design-time (Visual Studio) component.
Environment - Code intellisense
- JS intellisense
- Config intellisense
- Code behind
- Solution item templates and project templates
Controls
- Control is resizable
- Source code preservation
- Containers (both naming containers and not a naming container):i.e Table, Panel, Templates etc
- Chrome
- Right-click menu
- HTML intellisense
- Split view, Design view, HTML view switching
- Cut/Copy/Paste
- Drag/Drop
- Undo/redo
- Visible switch on the control
- White space preservation
Dialogs and custom editors
- Localized dialogs
- Truncated text
- Focus
- Tab order
- Default settings
- Buttons to close, help, minimize
- Accessibility
Global considerations
Here are some considerations you want to think about putting into your testplan.
Interesting areas to both controls and runtime features:
- Globalization/Localization including “Turkish I”
- Security
- Side-by-side
- Performance
- 64-bit issues
- OS-specific issues
- Data: Sql versions (2000, Yukon, katmai etc). Flavors (developer edition, express, etc)
- Data: Oracle, MySql, terradata, etc
- IPV6
- Error handling: are errors clear and actionable?