689: translations not generated for choice list used with search() [tests] #693
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.
Follow up to #690 to finish the test cases.
Why is this the best possible solution? Were any other approaches considered?
Covers use cases in relation to choice / translation behaviour per the XLSForm docs. I found the numbered list there a bit abstract, so for reference this docs page from SurveyCTO has good illustrations of the advanced usages.
What are the regression risks?
None, it's just tests.
Does this change require updates to documentation? If so, please file an issue here and include the link below.
Not directly, but I noticed a dead link on the XLSForms docs page. Not sure if the file is gone or it's a permissions issue:
Before submitting this PR, please make sure you have:
tests
nosetests
and verified all tests passblack pyxform tests
to format code