Add Mink integration test for Channels record tab.#5261
Open
demiankatz wants to merge 1 commit into
Open
Conversation
Member
Author
|
Since there has been a request for an 11.0.4 release, I'm retargeting this PR -- doesn't hurt to improve test coverage early. As of this writing, it sounds like the reported problem was a local issue rather than a core bug, but there's no harm in testing the condition to prevent future regressions. |
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
1 participant
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.
We received a report that the "more results" button was not working correctly in the Channels tab. This PR adds a Mink test to cover the functionality. However, the test is passing, so I have been unable to find a problem.
I created this test against the release-11.0 branch in case we found a bug that would justify an 11.0.4 release; however, since we have not yet discovered such a problem, I'm leaving this pointed at the dev branch and release 11.1 for now. It can be easily retargeted if we determine that there is a need.