Add Gherkin tests for testing CLI functionality about crc

[agajdosi]

@gbraad Sure, we can create a separate repository for it. Theoretically it might be even useful for other folks, so we might keep it as package and then import it + implement crc specific steps in crc repository. In both cases having it separate in the beginning could help the QE to develop stuff a little bit faster.

[tsedmik]

+1

[gbraad]

sounds good.

Should this be part of the general repo? or shall we go ahead and for now create a separate repo and see if we can pull it in later. It seems like it can run standalone... right?

[gbraad]

@agajdosi and might help to test crc also with other tools, like odo... or even only odo if they prefer so. ;-)

[agajdosi]

Hi @LalatenduMohanty, based on the conversation above, would it be possible to create a repository for integration tests inside code-ready organization? As the code might be useful for others, maybe naming could be clicumber?

Until then I am working on it here: https://github.com/agajdosi/clicumber.

[agajdosi]

@gbraad @LalatenduMohanty @tsedmik @jsliacan Would be nice to have the resolution on whether to add the tests in here or whether to keep the tests separated in specific repo (in that case we need to come up with the name for the repo and create the repository in the code-ready namespace). Can we agree on having the resolution on tomorrow morning?

[tsedmik]

I opt for having it as a separate project. It can be used by others - who want to create tests based on CLI with Cucumber support.

And I also like the name clicumber 👍

[gbraad]

Fixed by 3570232