test added for updating multiple flightpath docking widget for new operations (enabled signals and slots)#2358
Draft
ReimarBauer wants to merge 4 commits intoOpen-MSS:developfrom
Draft
test added for updating multiple flightpath docking widget for new operations (enabled signals and slots)#2358ReimarBauer wants to merge 4 commits intoOpen-MSS:developfrom
ReimarBauer wants to merge 4 commits intoOpen-MSS:developfrom
Conversation
added xfail for the test
Member
Author
|
@joernu76 this did not fix the issue but added the test and the infrastructure that it gets to the reload_operation function. Because @rohit2p has a project on the multiple flightpath docking widget and may came to the same problem, I guess there is a good chance that after the project this test also works. |
Member
Author
|
There is no need to merge this now. |
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
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.
Purpose of PR?:
Fixes #2269
Does this PR introduce a breaking change?
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Does this PR results in some Documentation changes?
If yes, include the list of Documentation changes
Checklist:
<type>: <subject>Starting with the test