Skip to content

Latest commit

 

History

History
48 lines (44 loc) · 1.9 KB

shinytest2-unit-testing-for-shiny.md

File metadata and controls

48 lines (44 loc) · 1.9 KB
talk_id talk_slug talk_type talk_tags session_slug talk_title talk_title_short talk_materials_url speakers
22115
shinytest2-unit-testing-for-shiny
regular
programming
shiny
big-shiny-apps
{shinytest2}: Unit testing for Shiny applications
shinytest2
name affiliation url username photo bio
Barret Schloerke
RStudio
barret_schloerke
/assets/img/2022Conf/_talks/22115_barret-schloerke.png
`hello()`! Dr. Barret Schloerke is a Shiny Software Engineer at RStudio. He currently maintains and creates many R packages surrounding the Shiny ecosystem, including `{shiny}`, `{shinytest2}`, `{reactlog}`, and `{plumber}`.

Manually testing Shiny applications is often laborious, inconsistent, and doesn’t scale well. Whether you are developing new features, fixing bug(s), or simply upgrading dependencies, it is critical to know when regressions are introduced. The new {shinytest2} R package provides a toolkit for unit testing Shiny apps and seamlessly integrates with {testthat}. Under the hood, it uses the new {chromote} R package to render apps in a headless Chrome browser with features such as live preview and built in debugging tools. In this talk, you’ll learn how to test Shiny apps by simply recording your actions as code and extending it to test more particular aspects of your app, resulting in fewer bugs and more confidence in future development.