Problem/Motivation
From #3358566: Plan to 8.x-1.5 release
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
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | current_page_crumb-basic-load-test-3391221-2.patch | 1.22 KB | ericgsmith |
Issue fork current_page_crumb-3391221
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:
Comments
Comment #2
ericgsmith commentedAdding a basic test - looks like automated testing isn't setup, would make sense to expand this to cover setting up gitlab ci
Comment #3
ericgsmith commentedComment #4
greg boggsLooks 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
Comment #7
prudloff commentedWe now have a working CI. I created a MR so that we can run the tests.
@ericgsmith would you still be interested in writing more tests?
Comment #8
liam morlandI suggest this be merged so that there is something. More tests can be added later.
Comment #9
prudloff commentedI'm not a huge fan of having a test that checks basically nothing.
I added a unit test based on PathBasedBreadcrumbBuilderTest and a functional test based on BreadcrumbTest from core.
Right now they mostly test that the module does not break the breadcrumbs. They should probably be extended to test that the module does its job correctly (adding the node title at the end) but this could be done in a followup.