Testing is enjoyable if you are using the right tools and technologies, of-course you also need to understand the philosophy behind the testing. I generally use testing tools interactively to try different options that the tool you are using gives as alternatives. For Selenium and Capybara, I have scripts to run get to get them ready on my console, you can read more this post for Windows and this for Unix-like. Under the quarantine days, I wanted to create a Ruby GEM for any want to get Capybara experience on the console for their project.
Capycon is simple, the short version of Capybara-Console, a GEM file so you can install it by:
gem install capycon
When you require the capycon, it automatically opens www.testrisk.com with Chrome driver by default. But you change the current driver by one of the following in the list. If you always want to open the URL as SITE_NAME that you generally test with the driver you want, you set them as environment variables in your bash_profile. For this run the following commands:
I will be appreciated to get feedback from you on GitHub.