Skip to content
This repository was archived by the owner on May 1, 2018. It is now read-only.

Conversation

@thejones
Copy link
Contributor

This code should accomplish two main things.

  1. Remove the ability to approve new members if the approved membership count is already the same as the business size.
  2. Remove the ability to set the business size lower than the approved count.

The individual user should not receive errors and will be added to the team. This allows users to start tracking commutes and puts the burden on the team Captain. The Captain can the approve, deny, or edit the business size.

I have all specs passing but only by modifying the participation calculator spec. (Adds 5 members and business size is set at 2). I am not sure if the spec is wrong or my code. I feel that by default the status is unapproved which should in theory not be affected by my code.

General

  • Verify new code in team and membership models

Testing:

  • Verify membership_spec is written correctly. I needed to create two users. One is the default and the other is user0
  • Review participation_calculator_spec if model code and validations seem correct.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The commented memberships should work if the business size here and the upper limit on the next line are bumped up to 5 or more.

@thorncp
Copy link
Contributor

thorncp commented Jul 10, 2014

The feature specs seem fine to me, but I'd like to see some model specs as well.

thejones added 3 commits July 22, 2014 11:17
Validates that the business size cannot be lower than the number of
approved members.
@thejones
Copy link
Contributor Author

Added two model specs, reformatted feature specs as needed and adjusted white space as needed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Delete this line.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants