Skip to content

ruby-joinville/workshop-invitation-challenge

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

29 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

You need some necessary skills to take full advantage of the workshop. In this challenge, we exercise some of these skills: git, basic GNU/Linux terminal, install and write the basic Ruby code.

Read all this README file, and follow these steps:

  1. Join the workshop event at Sympla;
  2. Fork this repository;
  3. Implement the missing code;
  4. Run tests and make sure they pass;
  5. Send the link of your cloned repository to [email protected].

Challenge

Inside the directory /lib/ you will find these files:

The purpose here is to implement correctly the methods that compose files tagged with [TODO]. The files tagged with [DONE] are already done, and you can read them to understand how to implement the other files.

Git/Github instructions

Fork this repository

To learn how to fork a repository, access GitHub documentation fork-a-repo and click on All tab to see how to do it by the graphics interface.

Clone the forked repository to your machine

To learn how to fork a repository, access GitHub documentation cloning-a-repository and follow instructions.

Implementing the challenge

You will need:

  • Basic Linux commands;
  • Technical English;
  • Learn basic Ruby.
Ruby

On Ubuntu, you can easily install Ruby with apt-get install ruby. You can also use the RVM tool, and install ruby version.

Solving the challenge

Take a look on square as an example of implementation.

Also, there are many documentations that you can take a look to learn the basics of Ruby:

Implement the code.

Before sending the code to us, make sure all test code pass

To prove you were able to implement the challenge correctly in Ruby, you will need to run the following tests with:

$ ruby test.rb

If you run these tests before your implementation, you'll see some errors like this below, because you didn't implement the code yet:

Start Status

After implementing the code, what we expect to see when running the tests is something like this:

Goals

Good luck, and Don't Panic!

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages