Write Acceptance Tests for Core Functionality

[vkoves]

To be able to move over to Vue.js and ensure that functionality is still working as desired (and to generally improve test coverage of Carpe and help make new deploys go more smoothly), I will be taking on writing acceptance tests for all core Carpe functionality. This issue serves as a definitive list that I check off as I work.

Please comment with any suggestions you have for further tests of core scheduler functionality, since that's where the Vue.js work will be taking place.

Scheduler UI

• [ ] Can view any date in the scheduler
  • [ ] Can press next to view the next week
  • [ ] Can press previous to view the previous week
  • [ ] Can type a date into the datepicker field and defocus to choose a date
• [ ] Can view events in weekly view
• [ ] Can view events in monthly view

Events

• [ ] Can create an event by dragging a category to the schedule, with the event getting its category’s color
• [ ] Can edit an event’s name inline by clicking event name, typing, and hitting Enter
• [ ] Can edit an event by clicking the edit icon
  • [ ] Can see the edit event overlay with the event’s category name
  • [ ] Can set the location, description, and name to text values
  • [ ] Can set the start and end time to valid time strings
  • [ ] Can set the repeat type of the event
  • [ ] Can add a break to the event
• [ ] Can delete an event by clicking the X icon

Categories

• [x] Can create a category and a new category is shown in the sidebar
• [x] Can edit a category
  • [ ] Can set the name, privacy and color with the changes saving
  • [ ] Can add a break to the category
• [x] Can delete a category and it disappears from the sidebar

Repeat Breaks

• [ ] Can manage (view) repeat breaks
• [ ] Can create a repeat break

Copied from my Vue.js Scheduler Planning

[vkoves]

My work on these tests can be found on the add-scheduler-acceptance-tests branch.