Issue #16012 has been updated by hsbt (Hiroshi SHIBATA).


Recently, I added `test-tool` target for the common library under the tool directory. We can test `rbinstall.rb` with it with the installation specification.

I know your concern. But your `ruby-head` only points Travis environment especially RVM. The some CI uses docker image provided the docker inc or the original images. The traditional CI like Travis or Azure Pipelines uses their internal environment or original distribution etc. We couldn't support all of the environments.

But I would like to add the system test for the ruby version managers with Docker like https://github.com/oracle/truffleruby/blob/master/doc/contributor/docker.md.

The system test was:

 * install ruby master used by ruby managers or make install.
 * assert installation files with the expected structures.
 * assert binstub behavior with ruby managers or not.


The additional works, We can test them with `--program-suffix`, `--prefix` and `DESTDIR` etc.

----------------------------------------
Feature #16012: Add a (small) test-install suite?
https://bugs.ruby-lang.org/issues/16012#change-79758

* 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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>