I have a good conceptual understanding of rspec and the reason we are using it but I need help with the first steps. The folder mentioned above includes a lib subfolder with the rb file for my work and a spec subfolder for testing. Any (dummy proof) help would be appreciated!
Click download link to download archived project folder
Open the folder in Finder (on Chrome I like to click the arrow next to the downloaded folder and click “Show in Finder”)
Double click the archive folder to extract the contents in the current directory
Open the Terminal application
Make sure the Terminal application is pinned to your dock for easy access by right clicking it in your dock and selecting Options > “Keep In Dock”
Drag the newly extracted folder from Finder down to your dock and drop it onto the Terminal application (this is an easy way to change directory into that folder!)
Run the bundle install command to install the gems specified by the Gemfile
Run thebundle exec rspec --color command to run your tests
Run the atom . command to open up the current directory in the atom text editor
Open the lib folder and write the code to pass the specs (Yay we are programmers!)
Return to the Terminal and run the specs again until everything is passing
Hey Luke, I have just been telling people to disable the Rubocop linter in settings > packages for now we can fix it when you start at App Academy. Until then, it is better practice to proof read your code and handle the errors if they come up.
Hi, I’ve been having a problem getting going with this as well. Typing bundle install just returns an error saying command not found. I’m just running ruby in a repl for now, but how can I get this working?
Unfortunately, it still isn’t working. Typing in bundle install simple says command not found. Is there something I’m supposed to be typing in alongside that?
@kevin This was massively helpful! Is it possible to add these notes to the alpha curriculum directly on the Methods Exercise page? I’m just starting the alpha course and was lost as to how to run code in the terminal until I read your steps, Kevin. I think it would be great for future learners to have these steps more explicitly outlined in the curriculum.