Fix search smoketests #599
Draft
Conversation
This file contains 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
…ch to in-memory to prevent goroutine leaks on tests
…hey use the same keybinding
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.
Path location of the site contents to index is now fixed by using the embed module.
Using an in-memory index instead of file because parallel access and updating to the index from the smoke tests was causing it to blow up.
Removed the ctrl + k shortcut on the search because it seemed to be breaking the bind key smoketest (? - may also be a flaky test).
Increased the debounce time
There was a few flaky tests I noticed:
TestExampleUpdateSignals
TestExampleImgSrcBind
TestExampleBadApple
TestExampleBindKeys
TestExampleClasses