# Application testing capabilities (urgent)

**URL:** <https://community.glideapps.com/t/application-testing-capabilities-urgent/8528>\
**Category:** Feature Requests\
**Created:** [May 5, 2020, 4:44pm UTC](https://community.glideapps.com/t/application-testing-capabilities-urgent/8528 "2020-05-05T16:44:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jrox10](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jrox10/32/6847_2.png) [@jrox10](https://community.glideapps.com/u/jrox10)\
**Post date:** [May 5, 2020, 4:44pm UTC](https://community.glideapps.com/t/application-testing-capabilities-urgent/8528/1 "2020-05-05T16:44:42Z")

</div>

**There’s a serious problem with Glide.**  
I currently have a PRO application that both I and the (corporate) users are very satisfied with. 🙂  
But when it comes to making changes, you have to make them on the production version, which **makes it very difficult** to include new functionality.  
What I do is use another application (more or less similar to PRO) with other test data, but this application is not PRO, and I cannot test many of the PRO features in the test application.

> This often means that I have to make changes directly on the production application and therefore risk breaking the application or losing data easily.

One (or all three) of these features would be required:

1. 
  - Test Environment (Pre, stage…or whatever you want to call it)

2. 
  - Possibility to export all the glide configuration in order to backup the application (the glide part) or to replicate the changes in another test application

3. -To be able to make a private copy of the application (not necessarily public) and to be able to change the data sheet to which it is associated
4. 
  - Capabilities to recover from a backup copy