Problem/Motivation

Currently this module has no testing at all - we should start by writing a test file to have in the repo that is the step to test before release manually. QA can then take this and move into functional testing.

Proposed resolution

Write a testing file

Issue fork ai_image_alt_text-3561670

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

marcus_johansson created an issue. See original summary.

marcus_johansson opened merge request !21

marcus_johansson’s picture

marcus_johansson commented
Status: Active » Needs review
anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Version: 1.0.1 » 1.0.x-dev
Status: Needs review » Needs work

Wouldn't it be better to just have these as automatic tests?

anybody’s picture

anybody
Primary language German
Location Porta Westfalica
commented
Status: Needs work » Postponed (maintainer needs more info)
Related issues: +#3574780: Fix code style (phpcs. phpstan, styleint, cspell, eslint, ...) and add tests for all functionalities

I think we might close this in favor of #3574780: Fix code style (phpcs. phpstan, styleint, cspell, eslint, ...) and add tests for all functionalities?