Modernize LibreSign Behat contexts and feature definitions for Behat 4

Open
#8,977 0 comments 0 reactions 0 assignees View on GitHub

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

backend enhancement php

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

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LibreSign/libresign

All issues in LibreSign/libresign

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.