Purpose Statement

• Provides secure access to two distinct First Due test environments (Test Daily and Test) that enable users to practice system features, conduct training exercises, and test configurations without affecting production data.

Background Information

• First Due maintains separate test environments that mirror the production system functionality
• Test sites are identical to the production environment but contain sample data that can be modified without consequences
• Two test sites are available: Test Daily and Test environments
• These environments are essential for onboarding new users, testing configurations, and training exercises
• Test sites help agencies maintain operational readiness while learning new features

Step-by-Step Guide

Accessing the Test Sites

• Navigate to your web browser
• Enter the appropriate URL based on your testing needs:
  • Test Daily Site: 
    
  • US Customers: US Test Daily
    
  • Canada Customers: Canada Test Daily
  • Test Site: 
    
  • US Customers: US Test
    
  • Canada Customers: Canada Test
• Use your assigned test credentials to log in
• Verify you see "TEST ENVIRONMENT" indicator on the interface
  

  

Understanding Reset Schedules

• Test Daily Site:
  • Automatically resets every night at midnight (system time)
  • All changes, configurations, and data entries are erased
  • Returns to baseline configuration each morning
  • Ideal for short-term training sessions and feature demonstrations
• Test Site:
  • Resets on the first day of each month
  • Maintains changes throughout the month
  • Suitable for extended training programs and multi-session courses
  • Allows for progression tracking over multiple training days

Recommended Usage

• Use Test Daily Site for:
  • Single-day training sessions
  • Quick feature demonstrations
  • Testing potentially disruptive configurations
  • Experimenting with system settings
• Use Test Site for:
  • Multi-week training programs
  • Progressive skill-building exercises
  • Department-wide training initiatives
  • Testing workflows that require data persistence

Best Practices

• Always verify you're in the test environment before making significant changes
  

 

• Document any important configurations before the reset period
• Coordinate with other users when using the Test site to avoid conflicts
• Use consistent test data patterns to make training exercises repeatable
• Create a training schedule that aligns with the reset cycles
• Export any useful reports or configurations before the reset occurs
• Inform all training participants about the reset schedule
• Keep test site credentials separate from production credentials
  

Troubleshooting & FAQs

Q: Why can't I access the test site with my production credentials?

• A: Test sites require separate credentials for security purposes. Contact your administrator or training officer to obtain test site login information

Q: My work from yesterday disappeared from the Test Daily site. What happened?

• A: The Test Daily site resets every night at midnight. All changes are erased as part of the automatic reset process. Use the Test site if you need data to persist longer

Q: Can I import real production data into the test site?

• A: While technically possible, it's recommended to use anonymized or sample data only. Consult with your administrator before importing any production data

Q: Which test site should I use for a week-long training course?

• A: Use the Test site (monthly reset) for any training lasting more than one day. This ensures continuity throughout your training program

Q: Are all features available in the test sites?

• A: Yes, test sites mirror the full functionality of the production system. However, some integrations with external systems may be limited or use test endpoints

Q: What happens if multiple people use the same test site simultaneously?

• A: Multiple users can access test sites simultaneously. Coordinate with other users to avoid conflicting changes, especially on the Test site

Use Case Examples

• New Employee Onboarding:

  • Use Test Daily site for initial system familiarization
  • Transition to Test site for role-specific training
  • Practice common workflows without risk

• Feature Testing Before Deployment:

  • Test new configurations in Test Daily site first
  • Validate workflows in Test site over extended period
  • Document successful configurations for production implementation

• Recurring Training Exercises:

  • Standardized daily drills using the Test Daily site
  • Monthly certification programs using the Test site
  • Department-wide refresher training sessions