How to Test Your DualEnroll.com Workflow
This guide walks you through setting up and testing your DualEnroll development environment. The development site is your sandbox for testing - you can create as much test data as needed without affecting your production environment.
Before You Begin
- You should have received an email invitation to confirm your account on your development site. Look for an email from the dualenroll platform and use it to log in and confirm your administrator account on the development site.
- Your development site URL will be: www.[your-domain].dev.dualenroll.com
Step 1: Set Up Your Catch-all Email Account
Before creating any test accounts, you must set up your catch-all email account. This account will receive all system-generated emails during testing.
1. Go to outlook.com and click "Sign In"
2. Use the credentials sent to you in the testing set up email.
3. Add this account to Outlook or your preferred email client, or simply log in on a private browser or different browser than you normally use.
4. Keep this email account accessible during testing - you'll need it to receive system notifications
Step 2: Create Your Administrator Account
1. Locate the invitation email from noreply@dualenroll.com
2. Click the "Click here to accept the invitation" link
3. On the new user registration page:
- Choose a login username (recommendation: use your college email address)
- Create a secure password
- Click "Register"
Step 3: Initial Platform Navigation
After logging in, familiarize yourself with the key areas:1. Admin Tab
- Check High Schools (ensure at least one is present)
- Review College Users (where you can invite additional testers)
- Verify Courses and Course Categories if applicable
2. Courses Tab
- Verify courses are present
- Check for course sections
- Note: If courses/sections are missing, you can add them manually using the "Add" button
Step 4: Set Up for Student Testing
For effective testing, set up your screen:
1. Keep your administrator view open in your current browser
2. Open a completely different browser (e.g., if using Chrome for admin, use Safari or Firefox for student testing)
3. If possible, use two monitors - one for admin view, one for student view
Step 5: Create a Test Student
In your second browser:
1. Navigate to your development site
2. Click "New Students" then "Create My DualEnroll Account"
3. For the student account:
- Use your catch-all email domain (e.g., @testde2.com)
- Create a systematic username (e.g., "TestStudent1[YourCollege]")
- Use a consistent test password you'll remember
- Select a partner high school
- Complete required fields (can use test data)
4. Check your catch-all email for the confirmation link
5. Copy the confirmation link and paste it in your student-testing browser
Step 6: Test the Application Process
As your test student:
1. Complete each application step
2. Note any fields that need customization
3. Validate that all required information is being collected
4. Check that validation rules work as expected
Step 7: Test Course Registration
1. Browse available courses
2. Select a course and section
3. Initiate registration
4. Monitor the progress in both views:
- Student browser: Watch status updates
- Admin browser: Monitor workflow progression
Step 8: Test Different Scenarios
Test various situations including:
1. **Happy Path**
- Complete successful registration
- Verify all steps complete as expected
2. **Alternative Paths**
- Test registration denials
- Try course prerequisite checks
- Test invalid student numbers
- Verify error messages
- Test sending items back for revision
Step 9: Customize Placeholder Content
In your admin view:
1. Go to Admin → Workflow Definitions
2. Review each step's content
3. Replace placeholder text with your institution's actual content:
- Update step instructions
- Customize email notifications
- Modify text message content
Best Practices for Testing
1. Keep Organized
- Use systematic naming for test accounts
- Document any issues you find
- Test one workflow at a time
2. Test Thoroughly
- Try every button and option
- Test both valid and invalid scenarios
- Verify all email notifications
3. Coordinate with Stakeholders
- Share access with relevant department members
- Collect feedback on workflow steps
- Verify data collection meets everyone's needs
Remember: The development site is your sandbox - you cannot break anything. Test thoroughly and create as much test data as needed to ensure everything works as expected.