This repository has been archived by the owner on Oct 20, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 5
Team Member Creates Available Time Slot through Calendar Invitation #13
Comments
maximegalon5
changed the title
Given a Team Member with a Public Schedule Link
Scenario: Team Member Creates New Available Time Slot through Invitation From Their Calendar
Apr 24, 2020
maximegalon5
changed the title
Scenario: Team Member Creates New Available Time Slot through Invitation From Their Calendar
Scenario: Team Member Creates New Available Time Slot through Invitation From Their preferred Calendar Application
Apr 24, 2020
zspencer
added
code
design
documentation
Improvements or additions to documentation
test
Work that will require testing skillz
@wip
We're working on it!
and removed
@future
labels
May 3, 2020
zspencer
added a commit
that referenced
this issue
May 3, 2020
See: #13 Also updates the default test script so that it doesn't try and run the work that is in progress when running feature tests.
cjoulain
pushed a commit
that referenced
this issue
May 4, 2020
…ar Invite (#24) * 🔧✅ Test creating an available time slot via calendar invite See: #13 Also updates the default test script so that it doesn't try and run the work that is in progress when running feature tests. * 🗃✅🌱🔧 Sprout Team Member Model (#26) * 🗃 Sprout Team Member Model - Small tweaks to scenario to make it terser - Initial model, factories, and spec file - Apply the migration and schema * ✅ Validate presence and uniqueness of the team member attributes We're relying on thoughtbot's shoulda matchers, because they're a well maintained set of expectation handlers that allow us to fluently describ a bunch of the validations that are built into Rails. * 🌱🔧 Seed a TeamMember when running db:seeds locally We like our seed files to give us a decent starting point for local development, as well as to be idempotent. This ensures that when we pick the project up in the future, we have a useful set of data to work with on our local machine without having to pull data from production. * 🔧✅ Sprout apiClient driver for feature tests We rely on drivers to interact with the system under test because that gives us a seam to implement API clients while we work forward. This prevents the common anti-pattern where a projects API and other implementation run faster than the documentation, api client, etc. It's not a panacea; but it gives us the affordances to notice when these test + document + implement gaps begin to emerge.
3 tasks
zspencer
changed the title
Scenario: Team Member Creates New Available Time Slot through Invitation From Their preferred Calendar Application
Team Member Creates Available Time Slot through Calendar Invitation
May 9, 2020
How does this sound from a "Short Blurb for Release Notes:" **New Feature: App-Free Scheduling!** It's tough balancing being available
for conversations with having focused time. Our new App-Free scheduling
feature _works with your existing calendar of choice!_
Invite your [availability email](#link-to-scheduling-settings-page) and we'll
automatically update your scheduling link with your new availability.
Need to cancel a time slot? Delete it from your calendar! It'll disappear from
your scheduling page lickety split! (Perhaps figuring out the release note message deserves it's own ticket, so the more wordsmithy focused folks can focus on it) |
There's a shift in behavior here which I think we should try and test too. User Experience? For example, the Team Member is going from an On-Demand Availability paradigm to one where the Team Member is Making Themselves Selectively Available akin to Office Hours. The Motivation here is different. The TAVI / Hooked framework will be different too. |
Perhaps we should highlight the workflow ie
|
I dig it! Updated the top-level issue with
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This Issue May Be Closed When
The text was updated successfully, but these errors were encountered: