# 🔬 Workflow QA
Quality assurance is a big topic for AWF. It's important that users can reliably run workflows and trust the outcomes of the workflows. Two important measures are in place to make sure the quality of workflows on AWF is high:
- integration testing
- different environments
Each workflow has an integration test setup which runs a workflow with predefined inputs and check whether the workflow produces the expected outputs. Running an integration test after making changes to the workflow ensures that the workflow still functions properly(for more on the integration test (click here)[/user_docs/content_creation/qa_test.md]).
AWF uses different environments for different types of development.
Apart from the production website environment of AWF awf.arup.com (opens new window), AWF also has a development environment (dev.awf.arup.com (opens new window)) and a staging environment (staging.awf.arup.com (opens new window)).
The development environment is used only for changes to the AWF system by the core team.
The staging environment is used by users creating their own workflow.
Here they can safely change and test their workflow without the risk of "real" AWF users running their workflow and expecting trustworthy results.
When the new workflow is done, an integration test is ran. When the integration test is passed, the workflow can be moved to the production environment.
If changes need to be made to the workflow the process repeats, changing the workflow on the staging environment first, running an integration test and pushing the workflow to production.
Now you know how the QA of AWF workflows is handled. If you are interested in creating your own workflow, please go to the next step.