testing staged changes

I’ve discovered BackstopJS recently and am trying to implement it in a project with a very high ratio of dynamic content (random feeds & co).

I would like to use BackstopJS in 2 steps:

• When a developer changes a file, I could detect the modified files a-la lint-staged and run backstopjs against these files in a husky pre-push hook.
• A travis CI instance connected to the github repo would run backstopJs against all pages of the application.

Can we handle the staged testing part without using the backstop.json file (which would be used on the ci) ? I’m currently thinking of adding documentation in each component file with metas for the scenarios, eg

/*
 * backstop-label: Contact page
 * backstop-url: /contact/
 * backstop-selectors: ["#contact"]
 */
import React, {Component} from "react";

export default class Contact extends Component {
  …
}

Then I’d be able to generate the label/url/referenceUrl/selectors objects for scenarios and rewrite the backstop.json file to test staged files.

I’m hoping that you have a better suggestion to handle this use-case to avoid the inline documentation overhead.

[AdrienLemaire]

Got it, thanks. Closing since this looks resolved, and will reopen if I don’t manage to implement it correctly 😃

[garris]

Ah, good. actually, you probably don’t even need to use an active script. Just include the --filter=<scenarioForComponentName> argument when invoking backstop. Way easier.