how to test

[ddanielsantos]

Lib

• [x] use snapshots and unit tests (see #23)

Built-in components

• [ ] add react-testing lib

Navigation

• [ ] use fixtures instead of deck.mdx
• [ ] create slides from them
• [ ] run cypress
• [ ] make assertions

[ddanielsantos]

Maybe cypress isn't the way to go

We can test more easily by unit testing the lib functions and using react-testing-library in the built-in components

[ddanielsantos]

But without Cypress we can't test navigation, the final testing setup can be a mix of those 3 strategies

[ddanielsantos]

react-testing-lib works for built-in components, but it isn't the right tool for Astro components.

the Astro team is planning some API to render components individually, this can lead to a proper tool for Astro component testing.

the only place that astro-deck actually needs to test a Astro component is the slide-wrapper layout, but its implementation isn't stable right now and may change to a react component (because we need to support slide gestures)

[ddanielsantos]

now, we also need to test the CLI, integration tests would be cool

[ddanielsantos]

https://www.smashingmagazine.com/2022/04/testing-cli-way-people-use-it/

[ddanielsantos]

basic config for CLI testing added at #68