- Pair, stage 2 project
- Due 6:00 PM Friday, March 22 2019
To practice working with APIs, we will utilize the API for a tool with which you already very familiar: Slack!
The application we build this week will be designed for humans to use. This means the format will be familiar to us, but it seems a little silly - why would you use the command line when you could just use the app?
However, there are many places where you might want to use Slack, where it doesn't make sense to have a human in the loop. For example, you might set up a continuous integration tool like Travis CI to run your tests automatically whenever you submit a pull request. Travis has the ability to post in your Slack channel when the tests are done, using the Slack API in a way similar to the way we will in this project.
- Sending requests to and receiving responses from an API
- Working with data from an external source
- Mocking an external dependency during testing
- Designing and implementing a program using inheritance
We will write a complete command-line application that interacts with Slack. This application will be able to:
- List users and channels
- See details about a user or channel
- Send a message to a user or channel
We have provided you with our standard Ruby project setup:
libandspecsfolderslib/slack.rbis the Ruby file you should use to run the program. There's a bit of code here already - do some research and find out what it does!specs/test_helper.rbsetup to use minitest, simplecov and VCR
- A
Rakefileand aGuardfile - A
.gitignorefile
Other than this environment, there is no pre-built code for this project. All the project code and all the tests are up to you to create!
This is a pair project, so you and your pair should:
- High-five
- Choose one person to fork this repository in GitHub
- Add the person who didn't fork the repository as a collaborator.
- Both partners will clone the forked repo:
$ git clone [YOUR FORKED REPO URL] - Both partners will follow the Slack Auth Setup instructions to allow your program to talk to Slack.
Since you'll be working with an external API, it will be good to have the documentation handy. The three endpoints this project will use are:
We will do an in-class design activity for this project. While you should read through these requirements before that exercise, we do not recommend beginning work until we have finished classroom work.
For this project, we have provided our standard test infrastructure:
- A
specs/folder containing atest_helper.rbfile, including- Minitest reporters
- Simplecov
- VCR
- A
Rakefile, allowing you to run tests viarake test - A
Guardfile, allowing you to watch tests viaguard
You do not need to test your main command loop, or the user interaction portions of your app. However, all other classes and helper methods should be thoroughly tested. Here are some tips:
- Follow TDD best practices (pseudocode, red, green, refactor)
- Add tests for all code you write
- Make sure all tests are green before pushing to GitHub
- Make sure all tests are green after you pull
As a user, when I launch this program...
- I should see information about how many channels and users were loaded
- I should then be given three options for how to interact with the program:
list userslist channelsquit
As a user who is at the program's input prompt...
- When I type
list users, I should see a list of all the users in the Slack workspace. This list should include username, real name, and Slack ID. - When I type
list channels, I should see a list of all the channels for that workspace. This list should include the channel's name, topic, member count, and Slack ID. - When I type
quit, the program should exit. - After completing any command other than
quit, the program should reprint the list of commands and ask for another input.
Hint: You may want to investigate the Table Print gem to handle formatting tables.
Vocab: channels and users are both recipients.
As a user at the input prompt...
- I should see three additional options:
select user: select a user as the current recipientselect channel: select a channel as the current recipientdetails: show details on the current recipient
- When I type
select user, I should be able to supply a username or Slack ID. The corresponding user should be the "selected" recipient. - When I type
select channel, I should be able to supply a channel name or Slack ID. The corresponding channel should be the "selected" recipient. - For selecting both users and channels, if no user/channel has that name or ID, the program should let me know and return to the main command loop.
- When I type
details, the program should print out details for the currently selected recipient. What information is printed depends on whether it's a channel or a user.- If no recipient is currently selected, the program should let me know and return to the main command prompt.
As a user at the input prompt...
- I should see one additional option:
send message. - When I type
send message, if a recipient is selected the program should ask me to type out a message, which will be sent to that recipient.- If no recipient is currently selected, the program should let me know and return to the main command prompt.
Don't even think about reading these until all the primary requirements are complete!
- As a user, I can change global settings for the program
- These settings include the username for the bot and an emoji to use as an icon
- When I change these settings, the program should save them in the JSON format in a file named
bot-settings.json. When I restart the program, it should reload those settings.
- As a user, I can see a history of messages sent to the currently selected recipient. If I change recipients, the message list should also change.
If you're done with all that, read through the list of other endpoints for the Slack API, find one that does something interesting, and add it to your program!
Check out the feedback template which lists the items instructors will be looking for as they evaluate your project.