Schedule

General schedule
PI 20
PI 21
PI 22
PI 23
Nov   CMS  
Login  
Dashboard   
Feb Assignments  May Launch Strategy
Settings 
Notifications
Aug Launch
Dec   Login  
Class Materials  
Mar Markbook  Jun Communications
BE Integration ↑


Jan   Class Materials  
iRead  
Apr Reports
BE Integration 
Jul Testing

Detailed schedule
Week Days Activity
Week 1-2
Preparation and Configuration

Preparation of the testing environment.
Definition of necessary variables for the application.
Week 3
Unit and Integration Testing

Execute automated unit tests, document, and correct any errors found.
Execute integration tests to validate interaction between modules, document, and correct any errors found.
Analysis of unit and integration test results, adjustments, and improvements based on the findings.
Week 4
System testing 

Execute system tests to validate the complete functionality of the platform, document, and correct any errors found.
Analysis of system test results, adjustments, and improvements based on the findings.
Week 5
Performance testing

Configuration of performance testing tools, definition of test scenarios.
Perform load tests, monitor system performance.
Analysis of performance test results and areas for improvement.
Week 6
Safety testing 

Configuration of security testing tools, definition of test scenarios.
Execute penetration and vulnerability tests, document and correct vulnerabilities found.
Analysis of security test results, implementation of additional security measures if necessary.
Week 7
User acceptance testing.

Setting up the environment for the user, selecting test cases based on user requirements.
Key users execute test cases, document, and correct errors found.
Analysis of results, final approval by users.
Week 8
Final review and preparation for deployment into production.

Final review of all test results, update of technical and user documentation.
Implementation of final adjustments based on test results, optimization of performance and security.
Planning and communication of the production deployment plan, final validation of the production environment.


Additional Considerations
  • Communication:
    • Maintain constant communication with the development and testing teams to quickly resolve issues.
    • Hold meetings to review progress and obstacles.
  • Flexibility:
    • The schedule is flexible to accommodate unforeseen events and new discoveries during testing.
  • Documentation:
    • Document all findings, errors, and adjustments made during the testing process.