Why gem management matters in Ruby - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to install a gem using Bundler.

Ruby

system('bundle [1] rails')

Drag options to blanks, or click blank then click option'

Alist

Bupdate

Cremove

Dinstall

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'bundle update' instead of 'bundle install' to add new gems.

The bundle install command installs gems listed in the Gemfile.

2fill in blank

medium

Complete the code to specify a gem version in the Gemfile.

Ruby

gem 'nokogiri', '[1] 1.12.5'

Drag options to blanks, or click blank then click option'

A>=

B<=

C~>

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using '==' which locks to an exact version, limiting updates.

The ~> operator specifies a version constraint allowing patch updates.

3fill in blank

hard

Fix the error in the Gemfile line to properly group gems for development and test.

Ruby

group :development[1] :test do
  gem 'rspec-rails'
end

Drag options to blanks, or click blank then click option'

Aor

B,

C&

Dand

Attempts:

3 left

💡 Hint

Common Mistakes

Using logical operators like 'and' or 'or' instead of commas.

Use a comma to list multiple groups in the group method.

4fill in blank

hard

Fill both blanks to check if a gem is installed and print its version.

Ruby

if Gem::Specification.find_by_name('[1]')
  puts Gem::Specification.find_by_name('[2]').version
end

Drag options to blanks, or click blank then click option'

Arails

Bnokogiri

Crspec

Dpuma

Attempts:

3 left

💡 Hint

Common Mistakes

Using different gem names in the two places causing errors.

Use the gem name consistently to check and print its version.

5fill in blank

hard

Fill all three blanks to add a gem with a specific version and group it for development only.

Ruby

group :[1] do
  gem '[2]', '[3] 2.3.0'
end

Drag options to blanks, or click blank then click option'

Adevelopment

Btest

C~>

Drails

Attempts:

3 left

💡 Hint

Common Mistakes

Putting the gem in the wrong group or using wrong version operators.

Group the gem 'rails' under development with version constraint '~> 2.3.0'.

Practice

1. Why is gem management important in Ruby projects?

easy

A. It makes Ruby code run faster automatically.

B. It keeps projects organized and ensures consistent gem versions.

C. It removes the need to write tests.

D. It converts Ruby code to another language.

Solution

1. Step 1: Understand gem management purpose

   Gem management helps keep track of which gems and versions a project uses.

2. Step 2: Identify benefits of organization

   Organizing gems prevents conflicts and ensures the project runs the same on all machines.

3. Final Answer:

   It keeps projects organized and ensures consistent gem versions. -> Option B

4. Quick Check:

   Gem management = organization and consistency [OK]

Hint: Gem management = organized gems and stable projects [OK]

Common Mistakes:

• Thinking gem management speeds up code automatically
• Believing gem management removes testing needs
• Confusing gem management with code translation

2. Which of the following is the correct way to specify a gem in a Gemfile?

easy

A. install gem rails version 7.0

B. require 'rails', version: '7.0'

C. gem 'rails', '~> 7.0'

D. add gem rails 7.0

Solution

1. Step 1: Recall Gemfile syntax

   In a Gemfile, gems are declared using the gem method with the name and version string.

2. Step 2: Match correct syntax

   gem 'rails', '~> 7.0' uses gem 'name', 'version' format which is correct.

3. Final Answer:

   gem 'rails', '~> 7.0' -> Option C

4. Quick Check:

   Gemfile gem syntax = gem 'name', 'version' [OK]

Hint: Gemfile uses gem 'name', 'version' format [OK]

Common Mistakes:

• Using commands like install or add inside Gemfile
• Using require instead of gem in Gemfile
• Incorrect version syntax

3. What will be the output of running bundle install in a Ruby project with a Gemfile?

medium

A. It installs all gems listed in the Gemfile and their dependencies.

B. It deletes all installed gems from the system.

C. It runs the Ruby program specified in the Gemfile.

D. It updates Ruby to the latest version.

Solution

1. Step 1: Understand the role of bundle install

   The command bundle install reads the Gemfile and installs required gems.

2. Step 2: Identify correct behavior

   It installs gems and their dependencies, not deleting or running code.

3. Final Answer:

   It installs all gems listed in the Gemfile and their dependencies. -> Option A

4. Quick Check:

   bundle install = install gems from Gemfile [OK]

Hint: bundle install installs gems from Gemfile [OK]

Common Mistakes:

• Thinking bundle install deletes gems
• Confusing bundle install with running Ruby code
• Assuming it updates Ruby version

4. Given this Gemfile snippet:

gem 'nokogiri', '~> 1.12'
gem 'rails', '6.1.4'

What is wrong with this Gemfile if you want to update nokogiri to version 1.13.0?

medium

A. You need to specify the Ruby version to update nokogiri.

B. You must remove the rails gem to update nokogiri.

C. The Gemfile syntax is incorrect and causes errors.

D. The version constraint '~> 1.12' prevents updating to 1.13.0.

Solution

1. Step 1: Understand '~>' version constraint

   The '~> 1.12' means allow updates up to but not including 1.13.0.

2. Step 2: Check if 1.13.0 is allowed

   Since 1.13.0 is outside '~> 1.12', it cannot update to that version.

3. Final Answer:

   The version constraint '~> 1.12' prevents updating to 1.13.0. -> Option D

4. Quick Check:

   Version constraint '~> 1.12' blocks 1.13.0 update [OK]

Hint: ~> limits updates to next minor version, blocking bigger jumps [OK]

Common Mistakes:

• Thinking rails gem affects nokogiri update
• Believing Gemfile syntax is wrong here
• Assuming Ruby version controls gem updates

5. You want to share your Ruby project with others and ensure they use the exact same gem versions. Which approach best achieves this?

hard

A. Use a Gemfile with version constraints and commit the Gemfile.lock file.

B. Only list gem names in the Gemfile without versions.

C. Install gems manually on each machine without a Gemfile.

D. Use system-wide gem installations without Bundler.

Solution

1. Step 1: Understand sharing gem versions

   To share exact gem versions, you need both Gemfile and Gemfile.lock files.

2. Step 2: Identify role of Gemfile.lock

   Gemfile.lock locks gem versions so others install the same ones.

3. Step 3: Evaluate options

   Using a Gemfile with version constraints and committing the Gemfile.lock ensures consistency across machines.

4. Final Answer:

   Use a Gemfile with version constraints and commit the Gemfile.lock file. -> Option A

5. Quick Check:

   Gemfile + Gemfile.lock = exact gem versions shared [OK]

Hint: Commit Gemfile.lock to share exact gem versions [OK]

Common Mistakes:

• Ignoring Gemfile.lock file
• Not specifying gem versions
• Installing gems manually on each machine