yaroslawww / laravel-dusk-reporter
Report generator for Laravel Dusk.
Installs: 6 125
Dependents: 0
Suggesters: 0
Security: 0
Stars: 2
Watchers: 2
Forks: 0
Open Issues: 0
Requires
- php: >=8.0
Requires (Dev)
- friendsofphp/php-cs-fixer: ^3.2
- laravel/dusk: ^6.0
- orchestra/testbench: ^6.23
- phpunit/phpunit: ^9.5
- vimeo/psalm: ^4.12
Suggests
- ext-imagick: Needed to support combined report screen.
README
Report will be saved in .md
files.
Installation
You can install the package via composer:
composer require --dev yaroslawww/laravel-dusk-reporter
Usage
Purge old data
When testing, the package adds content files, so you need to clear the directories before starting tests again
php artisan dusk-reporter:purge # or php artisan dusk-reporter:purge -y # or php artisan dusk-reporter:purge --path="/my/project/report"
1. Use trait TestWithDuskReport
in your dusk test case. This is optional, but it will be easy to rename the file.
//...
use LaravelDuskReporter\TestWithDuskReport;
abstract class DuskTestCase extends BaseTestCase
{
use TestWithDuskReport;
//...
}
2. You can override default configuration
Change store report folder, by default package use "base_path('storage/laravel-dusk-reporter')"
Reporter::$storeBuildAt = app_path('reports/dusk-report');
or
DUSK_REPORT_PATH=reports/browser-tests php artisan dusk --stop-on-failure
Change store screenshots folder, by default package use field "$storeBuildAt"
Reporter::$storeScreenshotAt = app_path('reports/dusk-screenshots');
By default package save link in .md
files as relative path, you can change it
Reporter::$screenshotRelativePath = false;
Change element to fit content (by default package use "body" tag)
Reporter::$getBodyElementCallback = function ($browser) {
return $browser->driver->findElement(WebDriverBy::id('someId'));
};
3. Create report
namespace Tests\Browser\CPD\Marketing;
//...
class HomePageTest extends DuskTestCase {
/** @test */
public function open_by_not_logged_user() {
$REPORT = $this->newDuskReportFile()
->h1( 'Home marketing page' )
->h2( 'Initial data' )
->p( "Open page by not logged user" );
$this->browse( function ( Browser $browser ) use ( $REPORT ) {
$browser->visit( new HomePage() )
// ...
->assertPresent( '@header' )
->assertPresent( '@footer' );
$REPORT->screenshot( $browser, ReportScreenshot::RESIZE_COMBINE )
// or
->screenshotWithVisibleScreen( $browser )
// or
->screenshotWithFitScreen( $browser )
// or
->screenshotWithCombineScreen( $browser )
// or
->screenshotWithCombineScreen( $browser, $suffix = 'additional_screen', $newLine = false);
} );
$REPORT->h3('Conclusion')->p('Test passed.');
}
}
4. Create report for one test file
By default, the package is designed to create one report for one test (since the phpunit re-creates the structure for
each test). But you can create one file for multiple tests using method duskReportFile
abstract class Page extends BasePage
{
use HasDuskReporter;
}
namespace Tests\Browser;
use Database\Seeders\DatabaseDuskCPDSeeder;
use Facebook\WebDriver\Exception\WebDriverException;
use Facebook\WebDriver\WebDriverBy;
use Illuminate\Foundation\Testing\DatabaseMigrations;
use LaravelDuskReporter\Reporter;
use Tests\Browser\Pages\Page;
use Tests\DuskTestCase;
class ReportableDuskTestCase extends DuskTestCase
{
use DatabaseMigrations;
protected function setUp(): void
{
parent::setUp();
Page::withDuskReporter( $this->setUpReportFileForClass() );
}
}
namespace Tests\Browser\Marketing;
class HomePageTest extends ReportableDuskTestCase {
$duskReportClassFilePath = 'Marketing';
/** @test */
public function open_by_not_logged_user() {
$this->browse( function ( Browser $browser ) {
$browser->visit( new HomePage() )
->assertPresent( '@header' )
->assertPresent( '@footer' )
->reportUserSeePage()
->reportAppend( function ( $reporter ) {
$reporter->p( 'My additional note.' );
} );
} );
}
public function testPageHasVideo() {
$this->browse( function ( Browser $browser ) {
$browser->visit( new HomePage() )
->assertPresent( '@marketing-video' );
// $browser->reportUserSeePage();
$this->duskReportFile()->h2( "Open page with video" )
->screenshotWithFitScreen( $browser )
->p('Some note');
} );
}
}
5. Disable reporting
Sometimes you need to cancel the creation of a report (for example, you want to make a quick test without generating a
report). Then just add a global variable DUSK_REPORT_DISABLED=1
or add it to .env.dusk.local
file. Also package
supports disabling only screenshots DUSK_SCREENSHOTS_DISABLED=1
DUSK_REPORT_DISABLED=1 php artisan dusk tests/Browser/CPD/Marketing/HomePageTest.php --stop-on-failure DUSK_SCREENSHOTS_DISABLED=1 php artisan dusk tests/Browser/CPD/Marketing/HomePageTest.php --stop-on-failure
Frontend generation
In some cases, you will need to show the report in HTML format. Usually it is convenient to use md->html compilers for this. For example, you can use vuepress
# Add vuepress if not exists
yarn add -D vuepress
Then add command to your package.json
# package.json
{
...
"scripts": {
...
"testsPreview:build": "cp -r vendor/yaroslawww/laravel-dusk-reporter/assets/.vuepress storage/laravel-dusk-reporter/ && VUEPRESS_BASE='/laravel-dusk-reporter-html/' VUEPRESS_DEST='public/laravel-dusk-reporter-html' vuepress build storage/laravel-dusk-reporter",
...
},
"devDependencies": {
...
"vuepress": "^1.5.4",
...
},
...
}
Then just run
yarn testsPreview:build