Add automated testing

Open on Drupal.org →

Created on 3 October 2023, over 1 year ago

Problem/Motivation

From 🌱 Plan to 8.x-1.5 release Fixed

Before we tag the release, we need someone to actually test the dev branch, try at least most of the pages that might be funky (/user, a page view, home, a taxonomy term, an edit form), and report back. It's quite common for base features to get broken in dev branch because each patch gets tested individually, but no one tests the entire module set once it's been merged in a complete release.

Proposed resolution

- Identify base features that should be covered by tests
- Add tests covering their functionality
- Review
- Commit

✨ Feature request

Status

Needs work

Version

1.0

Component

Code

Created by

🇳🇿New Zealand ericgsmith

Live updates comments and jobs are added and updated live.

Sign in to follow issues

Comments & Activities

Issue created by @ericgsmith
Comment over 1 year ago →
🇳🇿New Zealand ericgsmith
Adding a basic test - looks like automated testing isn't setup, would make sense to expand this to cover setting up gitlab ci
Status changed to Needs work over 1 year ago4:14am 3 October 2023
Comment over 1 year ago →
🇳🇿New Zealand ericgsmith
Comment over 1 year ago →
🇺🇸United States Greg Boggs Portland Oregon
Looks good. I'd say, we want a test that a crumb exists on a content page and that the text of the crumb equals the page title.

Ideally we probably want a test for:

1. A node page
2. A view page /node maybe?
3. A user profile page
4. A taxonomy term page
5. A translated node

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024