[SERVER-34332] Re-enable tests in the buildscripts_test suite Created: 05/Apr/18 Updated: 06/Dec/22 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | 3.7.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Robert Guo (Inactive) | Assignee: | Backlog - Server Tooling and Methods (STM) (Inactive) |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | stm | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Server Tooling & Methods
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
A number of tests are disabled in the python buildscripts test suite. Apart from buildscripts/tests/test_remote_operations.py, which requires ssh to be enabled locally, the other tests should be able to run with a new deployment of the toolchain and/or the modifying the file paths used in tests to use os.path.join instead of hardcoding in POSIX strings. |
| Comments |
| Comment by Steven Vannelli [ 10/May/22 ] |
|
Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions. |
| Comment by Max Hirschhorn [ 10/Apr/18 ] |
|
We could pip install the dependencies before running the buildscripts_test.yml suite since we've had trouble getting boto3 and mock installed in the toolchain everywhere. |