Draft
Conversation
Contributor
|
If you plan to going toward the 'clean tarantool state from inside tarantool' direction, I suggest to pay attention to our attempts to solve problems of the same kind in test-run:
However I'll warn: this is almost infinite road and the implementation always will be flawed. The reliable way is to actually run a separate tarantool instance. This, OTOH, leads to its own subtle differences (another working directory at least). I would think about usablity. Should the option be a user choise (command line option), a project wide configuration value (stored within the repository), a file/group/test scope configuration value? I don't know an answer, just highlighted that we should pay attention to this. |
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.
What has been done? Why? What problem is being solved?
I didn't forget about
Close #122