Puppetry
3.2.2
3.2.2
  • Welcome Puppetry
  • Getting Started
  • Project
  • Suite
  • Group
  • Target
    • Simple Target
    • iFrame Target
    • ShadowDOM Target
    • Chained Target
    • Shared Target
  • Test Case
  • Test Step / Action
    • Page Commands
    • Page Assertions
    • Target Commands
    • Target Assertions
  • Managing Records
  • Snippets
  • Running tests
    • Interactive Mode
    • Troubleshooting
  • Test Report
  • Export
    • Exporting as Jest Project (CI-friendly)
    • Exporting as Test Specification
  • Settings
  • Template Expressions
  • Testing Techniques
    • Testing Dynamic Content
    • Exhaustive Testing
    • Performance Testing
    • Visual Regression Testing
    • Testing Shadow DOM
    • Testing Google Analytics tracking code
    • Testing Chrome Extensions
    • Testing REST API
    • Mocking HTTP/S Requests
    • Testing Transactional Emails
      • Example with Restmail.net
      • Example with Mailinator
      • Example with IMAP bridge
      • Example with Google API
    • Testing Forms with Captcha
  • Version Control
  • Tips and Tricks
    • Embrace the Power of CSS
  • Command API
  • Test Application
Powered by GitBook
On this page

Was this helpful?

  1. Export

Exporting as Test Specification

PreviousExporting as Jest Project (CI-friendly)NextSettings

Last updated 5 years ago

Was this helpful?

You can export test suite(s) in a human-readable report, e.g. to share it with colleges, who have no experience with Puppetry.

Press Ctrl+Shift-E (⌘⇧E) or click on File/Export Project as... menu item:

Export Project modal window shows up.

Select format "test specification"

Now you just need to select a destination folder for the report and click Export button. You will have a text report like this:

Demo Project
environment: test

template variables:
   SANDBOX_BASEURL = https://puppetry.app/demo/

TodoMVC
   filename: todomvc.json
   timeout: 50000
   
   targets:
      FIRSTNAME_INPUT = #fname
      LASTNAME_INPUT = #lname
      MESSAGE_INPUT = #comment
      CONSENT_CHECKBOX = #consent
      OPTION_RADIO_1 = #option1
      ATTACHMENT_FILE = #attachment
      FORM = #form
      SUBMIT_BTN = #submit
      HEADER =  .todoapp .header
      NEWTODO_INPUT =  .todoapp .header input.new-todo
      MAIN = .todoapp > div > .main
      ....

   1. describe: Functionality

      1.1. test: No todos
         1.1.1. Set browser viewport as "1920x1080", "x1"
         1.1.2. Visit "http://todomvc.com/examples/react/#/"
         1.1.3. Wait until target "HEADER" appears on the page with timeout "30000ms"
            â–· Give React.js time to build the app
         1.1.4. Assert that target "HEADER" is "available" and "visible"
         1.1.5. Assert that target "MAIN" is "NOT available"
         1.1.6. Assert that target "FOOTER" is "NOT available"

Report Screenshots

You can extend the report with the automatically generated screenshots per every test step. Just check on the "run tests and generate step screenshots" option in the "Export project" moda window:

When exporting is done, you are going to find in the given destination folder screenshots named after the test steps indices:

If you open a screenshot corresponding a target command or assertion you will see the acting targert highlighted:

Export Project as...
Export project modal
Export as test specification
Tick it on to get generated step screenshots
Test step screenshots in file explorer
Action target is highlighted