Problem/Motivation

Similar to \Drupal\FunctionalJavascriptTests\JavascriptTestBase::createScreenshot it would be nice to have a little helper which spits
out the current page into a file, really similar to the verbose mode, but without requiring the verbose mode to actually be there.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#3 2793451-output-page.patch887 byteslarowlan

Comments

dawehner created an issue. See original summary.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Assigned: Unassigned » larowlan

ding ding

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Assigned: larowlan » Unassigned
Status: Active » Needs review
Issue tags: +needs backport to 8.2.x
StatusFileSize
new 2793451-output-page.patch887 bytes

Here's one I made earlier

dawehner’s picture

dawehner
Primary language German
commented

Mh, in my usecases I would like to actually specify the path where the HTML should be.

dawehner’s picture

dawehner
Primary language German
commented

@larowlan
What are your thoughts about that?

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

@dawehner - sure, we could make it an optional parameter right?

dawehner’s picture

dawehner
Primary language German
commented

+1

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

Why do we need this now that BrowserTestBase logs each and every page response with #2763401: PHPunit browser tests should log all Mink requests?

Or do you want to do it if $this->htmlOutputEnabled is false?

dawehner’s picture

dawehner
Primary language German
commented

Well, the debug logger doesn't work when you use an alternative php test runner, like the one build into PHPStorm.

klausi’s picture

klausi
he/him||they/them
Primary language German
Location 🇦🇹 Vienna
commented

According to rfay the newest PHPStorm release supports our custom output printer, please try that.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented

2016.3 doesn't support it yet, thanks to @benjy for testing

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jibran’s picture

jibran
he/him
Primary language Urdu
Location Toronto, Canada
commented
Status: Needs review » Closed (outdated)
Issue tags: -needs backport to 8.2.x

I think this can be closed now.