Skip to content

Latest commit

 

History

History

samples

Puppeteer Sharp Contributions Samples

The sample projects are divided into test frameworks used:

  • PuppeteerSharp.Contrib.Sample.Machine.Specifications
  • PuppeteerSharp.Contrib.Sample.MSTest
  • PuppeteerSharp.Contrib.Sample.NUnit
  • PuppeteerSharp.Contrib.Sample.SpecFlow
  • PuppeteerSharp.Contrib.Sample.Xunit

All projects runs the following scenarios:

  1. Search for Puppeteer Sharp on GitHub
  2. Check that the Puppeteer Sharp master branch builds
  3. Compare the Puppeteer and Puppeteer Sharp versions

Content

Machine.Specifications

Machine.Specifications does not support async / await.

You can work around this limitation with the Await and Await<T> extension methods.

✔️ You may use the sync versions of the extension methods from PuppeteerSharp.Contrib.Extensions and PuppeteerSharp.Contrib.Should.

MSTest

MSTest supports async / await.

❗ You must use the async versions of the extension methods from PuppeteerSharp.Contrib.Extensions and PuppeteerSharp.Contrib.Should!

NUnit

NUnit supports async / await.

❗ You must use the async versions of the extension methods from PuppeteerSharp.Contrib.Extensions and PuppeteerSharp.Contrib.Should!

SpecFlow

  • PuppeteerSharpRepoSteps.cs contains step definitions using the PuppeteerSharp.Contrib.Extensions + PuppeteerSharp.Contrib.Should libraries

SpecFlow supports async / await.

✔️ You may use the sync versions of the extension methods from PuppeteerSharp.Contrib.Extensions and PuppeteerSharp.Contrib.Should if you use Xunit as the unit test provider!

Xunit

Xunit supports async / await.

✔️ You may use the sync versions of the extension methods from PuppeteerSharp.Contrib.Extensions and PuppeteerSharp.Contrib.Should.