- 
                Notifications
    
You must be signed in to change notification settings  - Fork 60
 
test: handle everything with go test #137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test: handle everything with go test #137
Conversation
510da5f    to
    45def97      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi! Thank you for the patch. It is generally ok. But I have several questions.
- AFAIU we do not clear artifacts after testing is over, is this true
 - See comments bellow
 
45def97    to
    413bef4      
    Compare
  
    
          
 Yes, I'll change it UPD: clean work_dir after run  | 
    
413bef4    to
    bc75d65      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi!  I left several minor comments.
I approved this PR and suggest to ping a second reviewer.
b6f8631    to
    8314aa6      
    Compare
  
    | 
           I've added support for   | 
    
d708c20    to
    909543e      
    Compare
  
    | 
           Well, CI job failed, so it looks like I need to research so no flaky test will be introduced After I increased timeouts a bit, there was 20 consecutive CI runs without fails, so I think I won't waste any more time.  | 
    
922321c    to
    491e9aa      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
71e736d    to
    aa80991      
    Compare
  
    Before this patch, it was required to set up test tarantool processes manually (and also handle their dependencies, like making working dir). You can see an example in CI scripts. This patch introduces go helpers for starting a tarantool process and validating Tarantool version. Helpers are based on `os/exec` calls. Retries to connect test tarantool instance handled explicitly, see #136. Setup scripts are reworked to use environment variables to configure `box.cfg`. Listen port is set in the end of script so it is possible to connect only if every other thing was set up already. Every test is reworked to start a tarantool process (or processes) in TestMain before test run. To run tests, install all dependencies with running `make deps` and then run `make test`. Flag `-p 1` in `go test` command means no parallel runs. If you run tests without this flag, several test tarantool instances will try to bind the same port, resulting in run fail. Closes #107
aa80991    to
    bd1263f      
    Compare
  
    Added standard .luacheckrc config. Added indentation to box.once blocks. Fix trailing spaces and add missing spaces to mathematical expressions. Set global variables through rawset.
bd1263f    to
    861a33f      
    Compare
  
    
Before this patch, it was required to set up test tarantool processes
manually (and also handle their dependencies, like making working dir).
You can see an example in CI scripts.
This patch introduces go helpers for starting a tarantool process and
validating Tarantool version. Helpers are based on
os/execcalls.Retries to connect test tarantool instance handled explicitly,
see #136.
Setup scripts are reworked to use environment variables to configure
box.cfg. Listen port is set in the end of script so it is possibleto connect only if every other thing was set up already.
Every test is reworked to start a tarantool process (or processes) in
TestMain before test run.
To run tests, install all dependencies with running root folder
and then run
Flag
-p 1means no parallel runs. If you run tests without this flag,several test tarantool instances will try to bind the same port,
resulting in run fail.
Closes #107