Testing Key Functions After Deployment¶
After deployment or migration, verify the following areas:
1. Authentication & Authorisation¶
- Access the login page.
- Login with a known user account.
- Confirm role-based access restrictions (e.g. admin vs standard user).
2. Core Navigation¶
- Access key modules:
- Projects
- Clients and Suppliers
- Resources
- Timesheets
- Procurement (Requisitions, Purchase Orders, Goods Receipts)
3. Data Operations¶
- Create new records in key controllers.
- Edit and delete records where applicable.
- Confirm validations and business rules behave as expected.
4. Attachments / BLOBs¶
- Upload and download attachments in relevant screens (e.g. Goods Receipt, Payments, Person Resource profile picture).
- Confirm files are stored and retrieved correctly.
5. Reporting¶
- Run representative RDLC reports from
/reports. - Verify that data and formatting are correct.
6. Email¶
- Trigger an email action.
- Confirm messages are delivered and formatted properly.
Record the test results and any issues discovered before approving go-live.
7. If a Test Fails¶
Do not approve go-live until the cause is confirmed. Use the table below to identify the failure category and next step:
| Failure Type | Indicators | Next Step |
|---|---|---|
| Configuration issue | Connection errors, wrong data, email not sending | Check web.config settings; fix and retest |
| Data or schema issue | Missing records, application errors after restore | Check the Errors table for [Ref: guid] entries; escalate to Developer if schema-related |
| Deployment issue | Corrupted pages, missing modules | Redeploy from validated package; see Deployment Process — Rollback |
| Infrastructure issue | AppPool stopped, disk full | Follow the Incident Checklist |
8. Test Data Cleanup¶
Tests may create records (timesheets, requisitions, leave applications) and trigger real emails. Before approving go-live:
- Delete any test records created during smoke testing using the application UI.
- If testing was performed in a staging environment, drop and rebuild the database from a clean backup.
- Confirm that any test emails were not delivered to live external recipients (suppliers, staff). If they were, notify those recipients.