Modernize LibreSign Behat contexts and feature definitions for Behat 4
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- php
- Domain
- testing-qa
Research direction
Start by auditing the LibreSign-specific Behat contexts and feature definitions, comparing them with the established Behat 4 conventions and reusable primitives in libresign/nextcloud-behat. Review step bindings, responsibilities, structured inputs, and business-rule readability, then run the affected feature files and the complete Behat suite; done means conventions are followed without weakened assertions or changed product behavior.
Written by the indexing model from the issue text.
Description
Goal
Complete a focused audit of the LibreSign-specific Behat domain steps now that the Behat 4 mechanical migration has already been integrated in #9374.
Delivered
The Behat 4 migration adopted supported argument types and reused generic Nextcloud WebDAV steps.
Required before closing
- Inventory overlapping or ambiguous local step patterns and implementation-detail-heavy steps.
- Verify that generic Nextcloud primitives remain in
libresign/nextcloud-behat, with signing-specific behavior local. - Improve only confirmed design problems; preserve scenario behavior and test coverage.
- Run affected features and verify the full Behat 4 suite before declaring the audit complete.
Scenario-state/order defects belong to #8973; runner/sharding changes belong to #8975.
- Dominant language
- PHP
- Stars
- 844
- Forks
- 176
- Avg merge
- 14h 3m
- Merged PRs (30d)
- 344
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LibreSign/libresign
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
OpenSSL engine: leaf certificates get O=Internet Widgits Pty Ltd, ST=Some-State from system openssl.cnfPossibly taken @vitormattos claimed this 5 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#9366 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
LibreSign/libresign#9007 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LibreSign/libresign#8284 · 5 comments ·
Maintainers usually reply within 1 day
-
frontend javascript technical debt
Difficulty 5/5 Over a week Newbie friendliness 8/100
Maintainers usually reply within 1 day
All issues in LibreSign/libresign
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Automattic/blocks-engine#6318 ·
Maintainers usually reply within 1 day
-
[remove-resource] Delete Open Course Hub, Open Multicourse Hub, and Learn2 with GitSync skeletonsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
35-feedback
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day