Adagrams

At a Glance

• Pair, stage 2 project
• Due before class, Monday Februaray 25th

Introduction

An anagram is a word or phrase formed by rearranging the letters of a different word or phrase. Adagrams is a fictional game in which a player is given a random set of letters and must make an anagram using those letters. Adagrams has a specific scoring system, so that the player's submitted anagram scores points. The rules for Adagrams are roughly inspired by the "Letter Round" portion of the British game show Countdown.

While working on Adagrams, it may help to think of a physical metaphor for this game, such as other common word games like Scrabble or Bananagrams. These analog games all feature a pool of letter tiles that the player draws from.

In this version of Adagrams, we will only be working with the English alphabet.

Learning Goals

• Write Ruby code with methods that declare data, read data, and manipulate data
• Write Ruby code with methods that take in parameters, use parameters, and return manipulated data
• Use pair-programming techniques
• Instill the habit of running unit tests to verify that the program works as expected

Objective

We will make a Ruby implementation of Adagrams that runs in the command line.

The program should also pass the provided unit tests.

Getting Started

• From the project root, you are able to execute all of your specs by running rake in Terminal

For the curious about `rake`, click here

rake (official site) is a program that runs tasks that we define. In this case, we have a pre-defined task that executes the tests. By running rake, we are saying something like, "Please run the tasks, which includes the task that executes the tests."

Tests

We have provided unit tests for you to run. A complete project will pass all provided tests.

To run the tests, in the command line, navigate to the project root and then run the command $ rake (without the $. Remember, $ indicates that it is a command line command.)

When you first open the project and run the tests with rake, you should have 0 passing tests and 16 failures. You should see something similar to the following screenshots:

What do these errors mean? These errors should help guide you with the next step to completing the project.

The tests for this project are written in minitest, a testing framework by Seattle Ruby Brigade.

Do not move onto a new wave of requirements until the minimum requirements of the previous wave are complete and your specs are green across the board.

Here is what it looks like when all 16 tests are passing:

Pair Programming

Utilize good pair programming practices. Refer to articles from the Agile Alliance, the Agile Institute, and our own suggestions for pairing if you need a refresher for some best practices. Switch driver and navigator roles often. When there is uncertainty or confusion, step away from the keyboard and discuss, plan, and document on paper or whiteboard before continuing.

Driver Code

We have provided some driver code for your Adagrams game in the files wave-1-game.rb, wave-2-game.rb, wave-3-game.rb, and wave-4-game.rb. Running $ ruby wave-1-game.rb will begin a command-line game that uses your Adagrams code. The boilerplate code will break the first time you run it: working through the waves specified below should create a running version of the game. Implementing code to make this game run is not a substitute for making the tests pass. It is simply there for you and your pair to reference how the Game may run during each wave, to have better perspective of what your program can do, and to get some practice reading other peoples' code. We fully expect you to create the specified methods to specification and making the tests pass.

Setup Requirements

Setup For Collaboration

1. You'll be working with an assigned pair. High-five your pair.
2. Choose one person to fork the project repo.
3. Add the other person in the pair (who didn't fork) to the forked repo as a collaborator. Instructions here.
4. Pick one machine to work on for the first few days.
5. That machine will clone the forked repo: $ git clone [YOUR FORKED REPO URL]
6. cd into the dir created.

Note: At this point, we have to work off of one machine, and if we need to share code with each other, we need to do something awkward, unreliable, and slow, like email files of code to each other. Later this week, we'll learn how to get the code onto both machines and collaborate simultaneously using Git.

Setup a Pair Plan

First, come up with a "plan of action" for how you want to work as a pair. Discuss your learning style, how you prefer to receive feedback, and one team communication skill you want to improve with this experience.

Get Familiar

Take time to read through the Wave 1 implementation requirements and the tests for wave 1. Write down your questions, and spend some time going through your understanding of the requirements and tests with your pair. Make sure you both can run $ rake and see the tests fail.

Come up with a "plan of action" for your implementation with your pair.

If, after you and your pair have taken some time to think through the problem and would like direction for how to dissect the problem, or if you need clarity on the terms/vocabulary we used in this project, you can check out a small hint we've provided.

Implementation Requirements

Wave 1

Our first job is to build a hand of 10 letters for the user. To do so, add a method called draw_letters in adagrams.rb. This method should have the following properties:

• No parameters
• Returns an array of ten strings
  • Each string should contain exactly one letter
  • These represent the hand of letters that the player has drawn
• The letters should be randomly drawn from a pool of letters
  • This letter pool should reflect the distribution of letters as described in the table below
  • There are only 2 available C letters, so draw_letters cannot ever return more than 2 Cs
  • Since there are 12 Es but only 1 Z, it should be 12 times as likely for the user to draw an E as a Z
• Invoking this method should not change the pool of letters
  • Imagine that the user returns their hand to the pool before drawing new letters

Distribution of Letters

Letter : Qty.	Letter : Qty.
A : 9	N : 6
B : 2	O : 8
C : 2	P : 2
D : 4	Q : 1
E : 12	R : 6
F : 2	S : 4
G : 3	T : 6
H : 2	U : 4
I : 9	V : 2
J : 1	W : 2
K : 1	X : 1
L : 4	Y : 2
M : 2	Z : 1

Note: Making sure that the drawn letters match the rules of the letter pool can be straightforward or very difficult, depending on how you build the data structure for the letter pool. It is worth spending some time with your partner to think carefully about this.

Wave 2

Next, we need a way to check if an input word (a word a player submits) only uses characters that are contained within a collection (or hand) of drawn letters. Essentially, we need a way to check if the word is, indeed, an anagram of some or all of the given letters in the hand.

To do so, add a method called uses_available_letters? in adagrams.rb. This method should have the following properties:

• Has two parameters:
  • input, the first parameter, describes some input word, and is a string
  • letters_in_hand, the second parameter, describes an array of drawn letters in a hand. You can expect this to be an array of ten strings, with each string representing a letter
• Returns either true or false
• Returns true if every letter in the input word is available (in the right quantities) in the letters_in_hand
• Returns false if not; if there is a letter in input that is not present in the letters_in_hand or has too much of compared to the letters_in_hand

What Instructors Are Looking For

Check out the feedback template which lists the items instructors will be looking for as they evaluate your project.