Exam Services - Board Portal Release

Add additional automated testing to ensure base requirements and most common edge cases are covered

Relying solely on legacy code to determine “behind-the-scenes” actions, especially as processes have changed

Identifying single point of contact within the business line who is responsible for all decisions.

Solicit feedback on user design earlier in the development process

Allowing long periods of time between testing cycles

Identifying testers for the release, and reviewing the specific test cases and purposes of each so that testing is more fluent.

Restate and document requirements in advance of development

Provide regular updates to management on the status of the project(s)

Pre-deployment tasks (backing up code/databases, turning off site, restricting access to site)

14 minutes (0521 - 0535)

Deployment of new code and verification

19 minutes (0541 - 0600)

Deployment of database changes and verification

5 minutes (0557 - 0602)

Post Deployment tasks

Verification of new user creation process

9 minutes (0605 - 0614)

Verification of Application submission (UT-SSW)

12 minutes (0615 - 0627)

Verify access to Board Portal Application section (UT,CO,TX)

7 minutes (0628 - 0635)

Verify access and functionality of Approval submission

3 minutes (0638 - 0641)

Verify IRPT purchase process

5 minutes (0644-0649)

Verify score transfer process

5 minutes (0651 - 0656)

Verify redirect of Publication page

Did not work

Redirect from Publication page to ASWB.org did not function

Differences in Production and Test with site security settings and domain name parts

Deploy a secure pre-release site on the production server with similar domain setup and security to do final testing before release is scheduled.

Internal Revenue Report is not working correctly

Query was timing out when running report.

Investigate ways to quickly identify poor performing queries to make adjustments to ensure proper database performance

Password reset emails are not being sent. All other emails (new user email, submission confirmation, email receipts) have been verified as working in production

The password reset function utilizes a separate process from other email mechanisms due to the accessing and storing of passwords. A change to an associated process was made and the password reset function stopped working as it was not updated to interact with the updated process.

Convert emails to use the same method of sending emails

Add additional test cases to cover all email types (new user, lost username, lost password, application generated)

Some candidates completing a preapproval are not able to pay via money order (they are directed to the credit card screen)

The deployment system excluded an updated file needed to handle money order payments due to human error.

Add additional steps to the deployment testing process to identify files not properly visible to the deployment system