Koichi Nakashima

Hi, It's hard work to prepare images that support real use cases. because there are many shells and we don't know what package you need. Therefore, The Official Docker images...

When we think of unit testing, we test with test data. It is not a good idea to use sensitive information in tests. I believe that this is a feature...

> it looks very clunky when you see a long series of argument strings or multiline arguments being reprinted in a summary display of test results. I agree with your...

Yes, it should be `After`. (・ω

`Run if` is confusing, so I'm going to use `Only if`.

I released [shellmetrics](https://github.com/shellspec/shellmetrics) as alpha.

I am considering to implement the profiler process in C or any other language. This is expected to reduce the load and support for parallel execution. - https://stackoverflow.com/questions/8400530/how-can-i-tell-in-linux-which-process-sent-my-process-a-signal - https://stackoverflow.com/questions/6296374/how-in-perl-5-can-i-get-the-pid-of-the-process-who-sent-me-a-signal

I think it's better to implement a subset of regular expressions, but I also think we don't need pattern matching matcher for tests.

If the amount of output is large, embedding it in jUnit XML will cause a significant performance degradation. ```sh Describe 'test' It 'runs' When run cat long.txt The status should...

> ### Main issue > I agree that there should be no failure of ShellSpec in the last case, so something has to be done. Maybe make this embedding optional...