A modern programming language that makes developers happier.

kotlinlang

I am wondering why's everyone going after testing this week :laughing:

Released to production last week... time to start testing this week. :joy:

Just wanted to take a screenshot and it seems to be impossible outside of testing so I lookt into its implementation :man-shrugging::joy:

&gt; Just wanted to take a screenshot
You can use `TestComposeWindow` :slightly_smiling_face:
```val window = TestComposeWindow(width = 1024, height = 768)

window.setContent {

}

File(path).writeBytes(window.surface.makeImageSnapshot().encodeToData()!!.bytes)```

It has some bugs, so it is better to use it inside `SwingUtilities.invokeLater`. We will fix this in this <https://github.com/JetBrains/compose-jb/issues/486|issue>

Thanks <@U015TKX93PD> for this very clear example :pray: Would be really cool if this would find its way into the test documentation and if not I will personally create a pull request for it ^^

Additional question: Can we just create an skia surface, print our components to it and take a screenshot from that? (without creating a whole window)

&gt; Would be really cool if this would find its way into the test documentation
Very good idea, thanks :slightly_smiling_face:
<https://github.com/JetBrains/compose-jb/issues/368#issuecomment-811166809>

&gt; skia surface, print our components to it and take a screenshot from that? (without creating a whole window)
`TestComposeWindow` does exactly that. It doesn't create a whole window.

Very cool :+1:
ok sorry for misinterpreting the class name I will try it asap. 
Thanks :grin:

`SwingUtilities.invokeLater` is needed because we don't properly handle `mutableStateOf` observations in other threads than Swing thread.