Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: fix integration yaml syntax #1610

Merged
merged 2 commits into from
Feb 13, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion .github/workflows/integration.yml
Original file line number Diff line number Diff line change
Expand Up @@ -28,10 +28,16 @@ jobs:
strategy:
fail-fast: false
matrix:
server-versions: ['stable29', 'stable30' 'master']
server-versions: ['stable29', 'stable30', 'stable31', 'master']
php-versions: ['8.1']
databases: ['mysql']
include:
- server-versions: 'stable31'
php-versions: '8.4'
databases: 'pgsql'
- server-versions: 'stable31'
php-versions: '8.4'
databases: 'sqlite'
- server-versions: 'master'
php-versions: '8.4'
databases: 'pgsql'
Expand Down
18 changes: 9 additions & 9 deletions tests/integration/features/APIv1.feature
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Feature: APIv1
@api1
Scenario: User has initial table
Then user "participant1" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |

@api1
Scenario: User creates, rename and delete a table
Expand All @@ -22,7 +22,7 @@ Feature: APIv1
Then user "participant1" updates table with keyword "renamed table" set title "renamed table without emoji" and optional emoji ""
Then user "participant1" deletes table with keyword "without emoji"
Then user "participant1" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |

@api1
Scenario: Table sharing with a user
Expand All @@ -35,7 +35,7 @@ Feature: APIv1
| delete | 0 |
| manage | 0 |
Then user "participant2" has the following tables
| Tutorial | Ready to share |
| Welcome to Nextcloud Tables! | Ready to share |
Then user "participant1" sets permission "read" to 0
Then user "participant1" sets permission "update" to 0
Then user "participant2" has the following permissions
Expand All @@ -46,9 +46,9 @@ Feature: APIv1
| manage | 0 |
Then user "participant1" deletes table with keyword "Ready to share"
Then user "participant1" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |
Then user "participant2" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |

@api1 @table-sharing
Scenario: Inaccessible table sharing with a user
Expand All @@ -57,19 +57,19 @@ Feature: APIv1
When user "participant2" attempts to share the table with user "participant3"
Then the reported status is "404"
And user "participant3" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |

@api1
Scenario: Table sharing with a group
Given table "Ready to share" with emoji "🥪" exists for user "participant1" as "base1"
Then user "participant1" shares table with group "phoenix"
Then user "participant2" has the following tables
| Tutorial | Ready to share |
| Welcome to Nextcloud Tables! | Ready to share |
Then user "participant1" deletes table with keyword "Ready to share"
Then user "participant1" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |
Then user "participant2" has the following tables
| Tutorial |
| Welcome to Nextcloud Tables! |

@api1
Scenario: Create and check columns
Expand Down
4 changes: 2 additions & 2 deletions tests/integration/features/APIv2.feature
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ Feature: APIv2
@api2
Scenario: Test initial setup
Then user "participant1-v2" has the following tables via v2
| Tutorial |
| Welcome to Nextcloud Tables! |
Then user "participant1-v2" has the following resources via v2
| Tutorial |
| Welcome to Nextcloud Tables! |

@api2
Scenario: Basic table actions
Expand Down
Loading