-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for .xctestproducts
and Test Plan
#606
Conversation
@DavidAsulin1 Again, thank you for the contribution, on behalf of the team. Would you mind adding a UT that can cover the changed branches in the code? |
/azp run |
No pipelines are associated with this pull request. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
common/src/main/java/com/microsoft/hydralab/common/entity/common/TestTask.java
Show resolved
Hide resolved
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@hydraxman The changes I made are better suited for Integration Testing rather than Unit Testing. I updated the private |
Description
In this PR, I suggest adding support for the
.xctestproducts
package in XCTest. As I described in issue #583, usingxctestproducts
is more suitable for CI and also supports the Test Plan feature.Currently, in order to export the test products, one needs to package the Derived Data and the
.xctestrun
file. After this change, the user can choose to upload thexctestproducts
package, and we will detect it internally.One additional change on the UI side is regarding the Test Plan name. In case the test type is XCTest, the user can enter the test plan name, which we will use if the test package is of type
xctestproducts
.If we decide to proceed with this change, the Wiki page will need to be updated.
Linked GitHub issue ID: #583
Pull Request Checklist
Does this introduce a breaking change?
If this introduces a breaking change for Hydra Lab users, please describe the impact and migration path.
How you tested it
I test the change locally by uploading
xctestproducts
package and by choosing different test plans to executePlease check the type of change your PR introduces: