oliviertassinari
commented
7 years ago What generates the screenshots?
Hey @fatso83, that's an excellent question! There are many many different ways to take those screenshots. We gonna start documenting them. I like how next.js is showing a large range of integration project. Basically, here is some of the projects we want to cover.
I have seen three categories of tools so far:
- The ones that take Component as input (what used with @material-ui)
- The ones that take screenshots during the e2e tests (what used with @doctolib)
- The ones that take pages as input
We don't know the best solution to this problem, we are experimenting different ones. What's setup do you have for running tests?
I tried to get started with Argos CI and got as far as the
/<org>/<proj>/getting-startedwhich landed me here. It is impossible to understand what will create the screenshots. There is just talk of uploading through the cli.Usually something like this would require a server to generate the components on a separate page, which would then be processed by PhantomCSS or similar, etc. But this is highly project dependent stuff, and not something you touch upon at all in the material presented to the user. Which is why I have the growing suspicion that you might be able to take some shortcuts by scoping this down to some subsegment, like only projects relying on React where you can render PureComponents somehow.
Really, I have no idea ... which is a bit of an adoption stopper :-)