Screenshots are written to the same folder as the specification output.
<p concordion:assertTrue="#TEXT">false</p>
When run with this fixture in the
spec.concordion.ext.screenshot
package, there is one image written to
| Location |
|---|
| /spec/concordion/ext/screenshot/ScreenshotNaming_img1.jpg |
Screenshots within the same spec are numbered sequentially.
<p concordion:assertTrue="#TEXT">false</p> <p concordion:assertTrue="#TEXT">false</p>
When run with this fixture, this results in two images being included in the HTML output and saved to the sub-folder spec/concordion/ext/screenshot:
| Image name | Saved to disk? |
|---|---|
| ScreenshotNaming_img1.jpg | true |
| ScreenshotNaming_img2.jpg | true |
Image names start with the specification name so that they are unique within the package.
<p concordion:assertTrue="#TEXT">false</p>
When this snippet is run by a fixture named /fruit/GreenApple.html, it results in the image being written to the fruit folder:
| Image name | Saved to disk? |
|---|---|
| GreenApple_img1.jpg | true |
When subsequently run by a fixture named /fruit/RedApple.html, it results in the image being written to the fruit folder:
| Image name | Saved to disk? |
|---|---|
| RedApple_img1.jpg | true |