updated with shinytest2 link

posts/2024-03-01_rhino_shiny_app_validation/rhino_shiny_app_validation.qmd

@@ -48,7 +48,7 @@ When you first run `rhino::init()` inside your project's root directory, [Rhino]
 
 Rhino comes with [testthat](https://testthat.r-lib.org/) installed and introduces the `tests/` directory in your project. As part of the validation process, you want to test your requirements. With Rhino, all you need to do is create your test-\*.R files in tests/testthat directory and run [`rhino::test_r()`](https://appsilon.github.io/rhino/reference/init.html).
 
-Although shinytest2 tests can also be added with minimal effort ([How to use shinytest2](https://appsilon.github.io/rhino/articles/how-to/use-shinytest2.html)), one of the distinct features of Rhino is the ability to write end-to-end tests with Cypress out of the box. To learn more about how to write Cypress tests via Rhino, you can read more on [Write end-to-end tests with Cypress tutorial](https://appsilon.github.io/rhino/articles/tutorial/write-end-to-end-tests-with-cypress.html) in the documentation.
+Although [shinytest2](https://rstudio.github.io/shinytest2/) tests can also be added with minimal effort ([How to use shinytest2](https://appsilon.github.io/rhino/articles/how-to/use-shinytest2.html)), one of the distinct features of Rhino is the ability to write end-to-end tests with Cypress out of the box. To learn more about how to write Cypress tests via Rhino, you can read more on [Write end-to-end tests with Cypress tutorial](https://appsilon.github.io/rhino/articles/tutorial/write-end-to-end-tests-with-cypress.html) in the documentation.
 
 #### Continuous Integration via GitHub