github.com/gophercloud/gophercloud@v1.11.0/docs/contributor-tutorial/step-04-acceptance-testing.md (about)

     1  Step 4: Acceptance Testing
     2  ==========================
     3  
     4  If we haven't started working on the feature or bug fix, why are we talking
     5  about Acceptance Testing now?
     6  
     7  Before you implement a feature or bug fix, you _must_ be able to test your code
     8  in a working OpenStack environment. Please do not submit code which you have
     9  only tested with offline unit tests.
    10  
    11  Blindly submitting code is dangerous to the Gophercloud project. Developers
    12  from all over the world use Gophercloud in many different projects. If you
    13  submit code which is untested, it can cause these projects to break or become
    14  unstable.
    15  
    16  And, to be frank, submitting untested code will inevitably cause someone else
    17  to have to spend time fixing it.
    18  
    19  If you don't have an OpenStack environment to test with, we have lots of
    20  documentation [here](/acceptance) to help you build your own small OpenStack
    21  environment for testing.
    22  
    23  ---
    24  
    25  Once you've confirmed you are able to test your code, proceed to
    26  [Step 5](step-05-pull-requests.md) to (finally!) start working on a Pull
    27  Request.