From: Greg.mpls@... Date: 2019-07-20T03:10:53+00:00 Subject: [ruby-core:93858] [Ruby master Feature#16012] Add a (small) test-install suite? Issue #16012 has been updated by MSP-Greg (Greg L). An example test (no assert) that's currently failing, run from a trunk install ```ruby require 'tmpdir' Dir.mktmpdir 'test_bundler' do |dir| File.write 'Gemfile', '', mode:'wb' str = `bundle exec "bundle exec 'ruby -v'"` puts str puts str.strip == RUBY_DESCRIPTION end ``` ---------------------------------------- Feature #16012: Add a (small) test-install suite? https://bugs.ruby-lang.org/issues/16012#change-79757 * Author: MSP-Greg (Greg L) * Status: Open * Priority: Normal * Assignee: * Target version: ---------------------------------------- At various times there has been discussion about whether testing should require `make install`. Although I prefer to do testing using install (vs build), I see it as a choice, and not a requirement. From time to time various issues have arisen that cannot be found with 'build' testing. Often, these issues cause CI test failure with master/trunk/ruby-head in external repos. Sometimes people blame 'Core', other times Travis, or rvm. Regardless, it doesn't look good. So, might a small set of tests that check install functionality be added? It may need to be two separate (but equivalent) scripts. One for *nix, one for Windows. In ruby-loco, I'm using a ps1 script to check that CLI bin files work. As soon as the update is pushed here, I'll add a test for nested bundler commands... -- https://bugs.ruby-lang.org/ Unsubscribe: