External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-01-09 23:12:08 -03:30
Code Issues Packages Projects Releases Wiki Activity

fixing quotes to not fail smart quotes sanity test

Browse Source
This commit is contained in:
Jake Jackson 2020-10-01 15:32:43 -04:00
parent 1b6acdf84d
commit 427e1cd214
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
awx_collection/TESTING.md
View File

@ -9,7 +9,7 @@ When trying to fix a bug, it is best to replicate its behavior within a test wit
The unit tests are stored in the `test/awx` directory and, where possible, test interactions between the collections modules and the AWX database. This is achieved by using a Python testing suite and having a mocked layer which emulates interactions with the Tower API. You do not need a server to run these unit tests. The depth of testing is not fixed and can change from module to module.
Let’s take a closer look at the `test_token.py` file (which tests the `tower_token` module):
Let's take a closer look at the `test_token.py` file (which tests the `tower_token` module):
```
from __future__ import (absolute_import, division, print_function)
@ -56,7 +56,7 @@ A completeness failure will generate a large ASCII table in the Zuul log indicat
![Completeness Test Output](images/completeness_test_output.png)
To find the error, look at the last column and search for the term “failure”. There will most likely be some failures which have been deemed acceptable and will typically say “non-blocking” next to them. Those errors can be safely ignored.
To find the error, look at the last column and search for the term "failure". There will most likely be some failures which have been deemed acceptable and will typically say "non-blocking" next to them. Those errors can be safely ignored.
## Integration Tests