Workbench: Invalid path to Chrome

[nick-youngblut]

I'm running shinytest2 v0.2.0 on Posit Workbench installed on a Ubuntu server. When running shinytest2::record_test(), I get the error:

Caused by error in `initialize()`:
! Invalid path to Chrome

I get that chrome is not installed on Ubuntu by default, but there doesn't seem to be any info the shinytest2::record_test() function docs or the shinytest2 docs on how to setup shinytest2 for Workbench.

sessionInfo

R version 4.2.1 (2022-06-23)
Platform: x86_64-pc-linux-gnu (64-bit)
Running under: Ubuntu 22.04.1 LTS

Matrix products: default
BLAS:   /usr/lib/x86_64-linux-gnu/openblas-pthread/libblas.so.3
LAPACK: /usr/lib/x86_64-linux-gnu/openblas-pthread/libopenblasp-r0.3.20.so

locale:
 [1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C               LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8    
 [5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8    LC_PAPER=en_US.UTF-8       LC_NAME=C                 
 [9] LC_ADDRESS=C               LC_TELEPHONE=C             LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C       

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
 [1] heatmaply_1.4.0       viridis_0.6.2         viridisLite_0.4.1     tidygraph_1.2.2       ggrepel_0.9.2         ggtree_3.6.2         
 [7] tidytree_0.4.2        treeio_1.22.0         ape_5.6-2             pool_0.1.6            data.tree_1.0.0       lubridate_1.9.0      
[13] timechange_0.1.1      memoise_2.0.1         tidytable_0.9.1       data.table_1.14.6     plotly_4.10.1         ggplot2_3.4.0        
[19] visNetwork_2.1.2      reactable_0.4.1       shinyTree_0.2.7       shinyWidgets_0.7.5    shinycssloaders_1.0.0 shinyBS_0.61.1       
[25] dbplyr_2.2.1          dplyr_1.0.10          RPostgres_1.4.4       DBI_1.1.3             config_0.3.1          shiny_1.7.4          
[31] aws.signature_0.6.0   aws.s3_0.3.21         httr_1.4.4           

loaded via a namespace (and not attached):
 [1] websocket_1.4.1     colorspace_2.0-3    ellipsis_0.3.2      base64enc_0.1-3     fs_1.5.2            aplot_0.1.9        
 [7] rstudioapi_0.14     bit64_4.0.5         chromote_0.1.1      fansi_1.0.3         xml2_1.3.3          codetools_0.2-18   
[13] cachem_1.0.6        shinytest2_0.2.0    jsonlite_1.8.4      compiler_4.2.1      backports_1.4.1     assertthat_0.2.1   
[19] fastmap_1.1.0       lazyeval_0.2.2      cli_3.5.0           later_1.3.0         htmltools_0.5.4     tools_4.2.1        
[25] igraph_1.3.5        gtable_0.3.1        glue_1.6.2          Rcpp_1.0.9          jquerylib_0.1.4     vctrs_0.5.1        
[31] nlme_3.1-157        iterators_1.0.14    stringr_1.5.0       ps_1.7.2            brio_1.1.3          testthat_3.1.6     
[37] shinyvalidate_0.1.2 mime_0.12           lifecycle_1.0.3     renv_0.15.5         dendextend_1.16.0   ca_0.71.1          
[43] scales_1.2.1        TSP_1.2-1           hms_1.1.2           promises_1.2.0.1    parallel_4.2.1      RColorBrewer_1.1-3 
[49] yaml_2.3.6          curl_4.3.3          gridExtra_2.3       ggfun_0.0.9         yulab.utils_0.0.6   sass_0.4.4         
[55] stringi_1.7.8       foreach_1.5.2       checkmate_2.1.0     seriation_1.4.0     rlang_1.0.6         pkgconfig_2.0.3    
[61] lattice_0.20-45     purrr_1.0.0         patchwork_1.1.2     htmlwidgets_1.6.0   bit_4.0.5           tidyselect_1.2.0   
[67] processx_3.8.0      magrittr_2.0.3      R6_2.5.1            generics_0.1.3      pillar_1.8.1        withr_2.5.0        
[73] tibble_3.1.8        crayon_1.5.2        utf8_1.2.2          grid_4.2.1          blob_1.2.3          callr_3.7.3        
[79] digest_0.6.31       webshot_0.5.4       xtable_1.8-4        tidyr_1.2.1         httpuv_1.6.7        gridGraphics_0.5-1 
[85] munsell_0.5.0       registry_0.5-1      ggplotify_0.1.0     bslib_0.4.2  

[schloerke]

This is not a {shinytest2} bug. The underlying bug is in {chromote}. Transferred issue.

[shahreyar-abeer]

Hi @nick-youngblut Were you able to find some workaround to run shinytest2 on Posit Workbench until the issue has been solved?

[nick-youngblut]

@shahreyar-abeer No, I was not. I just don't use shinytest2