Magento Test Server
A test server is where new updates, features, and mechanics are tested before being released on the main server. A Magento test server is part of the staging and testing environment for development.
Developers run tests required to check the quality before changes getting deployed to the production system.
Isolated System
Get an isolated environment for debugging and creating changes. The test system provides a separate and clean space from the production servers on a separate instance.
Zero Downtime
Magento stores rely heavily on performance and site availability. The test server ensures that the code works perfectly and does not affect response times.
Security
The test system is a clone of the live environment, so all the data is copied as it is. The test environment can only be reached via VPN, so no search engine or customer gets access to it.
How it works
Magento changes are made in the local environment first. It is deployed to the test/staging system using MGT Code Deploy. If the tests are successful, the code gets deployed to the production environment for end-users.
Benefits
Detect Bugs
Test the code for bugs during debugging and fix them on the test server. It helps detect errors and ensure code quality before reaching the end user.
Zero Downtime
Magento stores rely heavily on performance and site availability. The test server ensures that the code works perfectly and does not affect response times.
Omnichannel Testing
Test the code across multiple devices and ensure a smooth user experience. Analyze how users respond to changes delivered on different channels.
Experiment
Try different tech stacks and versions on the test server and promote innovation. It is not possible to use different stacks on the main servers.
Collaboration
Make different groups for development and tests. Collaborate freely on the test server and ensure the code works well for real-world usage.
FAQs
The MGT team will copy the code and Magento database onto a well-configured test server.
No, the code-related issues are handled by your developers. MGT takes care of all server-related issues.
The deployment tool is shared between the production and testing servers. Each production and test deployment runs in an isolated environment. So the changes do make in one environment do not affect the other.
Yes, our team manually scales the server based on the requirements.
We recommend workflow environments that have local development, staging, and production.
The different environments include -
Local development environment
A local development environment is a way to configure services on a local machine. It does not require external hosting, making it possible to work on the local computer.
The local environment has the same components as a live server. The developers are free to build code and test new Magento features.
Staging environment
Once the new code is tested locally, we move it to the staging environment. We perform Quality Assurance (QA) tests in the staging environment.
It may include Magento dev tests such as -
- Integration tests
- Compatibility
- Performance testing
- Running unit tests
- Javascript tests
- Magento functional testing framework
- Performance toolkit
The staging environment is the last step before something goes into production. It is a replica of the live site where we focus on testing specific code changes.
Production environment
Once the code is tested and approved, it is moved into the live or production environment.
In this stage, the changes are visible to end-users. If the testing is successful in the previous environments, the users get the new changes without any bugs.
For multi-server premium and ultimate hosting plans, there are 1x test servers. For AutoScaling plans, there are up to 3x test servers available. Test servers are useful for complex and large-scale Magento websites that make frequent changes.
Yes, the test server is a single-server environment with MGT Control Panel.
It is built for the cloud and offers specific features for hosting Magento on AWS. Manage instance upgrades and plan estimated peaks of server usage.
The dashboard shows the hostname, IP address, instance ID, and instance type. The monitoring section displays CPU utilization, memory consumption, and used disk space.
MGT CloudPanel offers a clean interface and command line options to handle several server management tasks.
Yes, the test system is a copy of the production environment. It has the same technology stack used in the live server.