Add automated testing

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

Active

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024