112 lines
4.7 KiB
Gherkin
112 lines
4.7 KiB
Gherkin
Feature: decks
|
|
|
|
Background:
|
|
Given user "admin" exists
|
|
Given user "user0" exists
|
|
|
|
Scenario: Create a new board
|
|
Given Logging in using web as "admin"
|
|
When creates a board named "MyBoard" with color "000000"
|
|
Then the response should have a status code "200"
|
|
And the response Content-Type should be "application/json; charset=utf-8"
|
|
And the response should be a JSON array with the following mandatory values
|
|
|key|value|
|
|
|title|MyBoard|
|
|
|color|000000|
|
|
|
|
Scenario: Fail to create a board with invalid parameters
|
|
Given acting as user "user0"
|
|
When creates a board named "This is a very ong name that exceeds the maximum length of a deck board created which is longer than 100 characters" with color "ff0000"
|
|
Then the response should have a status code 400
|
|
When creates a board named "Example board" with color "invalid"
|
|
Then the response should have a status code 400
|
|
|
|
Scenario: Fail to create a list with invalid parameters
|
|
Given acting as user "user0"
|
|
And creates a board named "MyBoard" with color "000000"
|
|
When create a stack named "This is a very ong name that exceeds the maximum length of a deck board created which is longer than 100 characters"
|
|
Then the response should have a status code 400
|
|
|
|
Scenario: Fail to create a card with invalid parameters
|
|
Given acting as user "user0"
|
|
And creates a board named "MyBoard" with color "000000"
|
|
And create a stack named "ToDo"
|
|
When create a card named "This is a very ong name that exceeds the maximum length of a deck board created which is longer than 255 characters This is a very ong name that exceeds the maximum length of a deck board created which is longer than 255 characters This is a very ong name that exceeds the maximum length of a deck board created which is longer than 255 characters"
|
|
|
|
Scenario: Cannot access card on a deleted board
|
|
Given acting as user "user0"
|
|
And creates a board named "MyBoard" with color "000000"
|
|
And create a stack named "ToDo"
|
|
And create a card named "Overdue task"
|
|
And remember the last card as "deletedCard"
|
|
And uploads an attachment to the last used card
|
|
And remember the last attachment as "my-attachment"
|
|
And post a comment with content "My first comment" on the card
|
|
And delete the board
|
|
|
|
When fetching the attachment "my-attachment" for the card "deletedCard"
|
|
Then the response should have a status code 403
|
|
|
|
When get the comments on the card
|
|
Then the response should have a status code 403
|
|
|
|
When post a comment with content "My second comment" on the card
|
|
Then the response should have a status code 403
|
|
|
|
When uploads an attachment to the last used card
|
|
Then the response should have a status code 403
|
|
|
|
When set the description to "Update some text"
|
|
Then the response should have a status code 403
|
|
|
|
When get the card details
|
|
Then the response should have a status code 403
|
|
|
|
When create a card named "Overdue task"
|
|
Then the response should have a status code 403
|
|
|
|
When create a stack named "ToDo"
|
|
Then the response should have a status code 403
|
|
|
|
Scenario: Cannot access card on a deleted card
|
|
Given acting as user "user0"
|
|
And creates a board named "MyBoard" with color "000000"
|
|
And create a stack named "ToDo"
|
|
And create a card named "Overdue task"
|
|
And remember the last card as "deletedCard"
|
|
And uploads an attachment to the last used card
|
|
And remember the last attachment as "my-attachment"
|
|
And post a comment with content "My first comment" on the card
|
|
When get the activities for the last card
|
|
Then the fetched activities should have 3 entries
|
|
And delete the card
|
|
|
|
When get the activities for the last card
|
|
Then the fetched activities should have 0 entries
|
|
|
|
When fetching the attachment "my-attachment" for the card "deletedCard"
|
|
Then the response should have a status code 403
|
|
|
|
When get the comments on the card
|
|
Then the response should have a status code 403
|
|
|
|
When post a comment with content "My second comment" on the card
|
|
Then the response should have a status code 403
|
|
|
|
When deleting the attachment "my-attachment" for the card "deletedCard"
|
|
Then the response should have a status code 403
|
|
|
|
When uploads an attachment to the last used card
|
|
Then the response should have a status code 403
|
|
|
|
When get the card details
|
|
Then the response should have a status code 403
|
|
|
|
# We currently still expect to be able to update the card as this is used to undo deletion
|
|
When set the description to "Update some text"
|
|
Then the response should have a status code 403
|
|
When set the card attribute "deletedAt" to "0"
|
|
Then the response should have a status code 200
|
|
When set the description to "Update some text"
|
|
Then the response should have a status code 200
|