You'll do that just as if you'd restore your production environment after a failure. I hope you've tested that procedure.

I have the habit or allowing people to call something a backup only if they have recently demonstrated that they can use that collection of data to restore a fully functioning system.

And that restore typically is done to a completely new system that includes everything from load balancer to persistence (e.g. database, document storage, search index).

That being said, backup instructions are here. For restoring on a test system: Make sure to anonymize the data and configure your test system in a way that it doesn't send email (or other) notifications to a legitimate production system user.

Assuming that the different environments are on different SQL Servers (or at least on different Instances), then would recommend that you keep the database names on all environments exactly the same. Use permissions (e.g. Integrated security) to ensure that only the correct environment systems and users access the appropriate environment databases.

1. Create a copy-only backup of an operational database suitable for use by: 
2. Install this backup on a different SQL Server as a discardable clone.