test(mac): add unit tests to validate first calls to compliance check#11724
Merged
test(mac): add unit tests to validate first calls to compliance check#11724
Conversation
Also makes public the description method used for logging. A private description method may have been an issue with the older logging code. To build successfully with Xcode, it was necessary to change runOnlyForDeploymentPostprocessing=1. This was apparently needed because of the upgrade to Xcode 15
User Test ResultsTest specification and instructions User tests are not required |
break into separate PR
mcdurdin
approved these changes
Aug 21, 2024
Collaborator
|
Changes in this pull request will be available for download in Keyman version 18.0.98-alpha |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This was intended to isolate and fix #11674, but these additional tests did not expose that issue. However, these tests are still useful for ensuring that the compliance object is safely created in different scenarios.
Also makes public the description method used for logging.
@keymanapp-test-bot skip