We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi.
Just a little reflection. Why not provide a system that allow you to describe some scenarios to execute before to crawl urls.
For example :
// MyProject/centipede.php $scenarios = new Centipede\Scenario\Collection(); $scenarios->add('customer_account', function ($browser) { $broswer->visit('/login'); $broswer->fillIn('login', 'account@email.com'); $broswer->fillIn('password', 'strong_password'); $broswer->press('Connection'); $broswer->visit('/account'); }); $scenarios->add('backoffice', function ($browser) { $broswer->visit('/admin/login'); $broswer->fillIn('seller[uuid]', '1122334455'); $broswer->fillIn('seller[password]', 'strong_password'); $broswer->press('Access to dashboard'); $broswer->visit('/admin/dashboard'); }); $scenarios->add('public', function ($browser) { $broswer->visit('/'); }); return $scenarios;
And then, the crawler will execute scenarios one by one and crawl urls each time.
The text was updated successfully, but these errors were encountered:
Yes, this would be interesting approach. In this case browser must share same session with guzzle client used in centipede crawler.
It is in deed simple extension point without reinventing the wheel, I like it.
Thanks @PedroTroller!
Sorry, something went wrong.
You could use Symfony's Client and DomCrawler classes for this (even if not asynchronous).
No branches or pull requests
Hi.
Just a little reflection. Why not provide a system that allow you to describe some scenarios to execute before to crawl urls.
For example :
And then, the crawler will execute scenarios one by one and crawl urls each time.
The text was updated successfully, but these errors were encountered: