VIP Report

Verified Installation of Posit

Deployment: CI Connect 2026.03.0 + PM 2024.08.0-6 Generated: 2026-03-26 00:08:53 UTC

Products Under Test

Product URL Version
Connect http://localhost:3939 2026.03.0
Package Manager http://localhost:4242 2024.08.0-6

Summary

Metric Count
Total 9
Passed 5
Failed 1
Skipped 3
Status FAIL

Results by Category

Connect

1 tests — 1 passed

PASSAPI key authentication works
tests/connect/test_auth.py::test_connect_login_api
Test procedure
  • Given Connect is accessible at the configured URL
  • And a valid API key is configured
  • When I request the current user via the API
  • Then the API returns user information

Package Manager

4 tests — 2 passed, 2 skipped

PASSCRAN mirror is accessible
tests/package_manager/test_repos.py::test_cran_mirror
Test procedure
  • Given Package Manager is running
  • When I query the CRAN repository for the "Matrix" package
  • Then the package is found in the repository
SKIPPyPI mirror is accessible
tests/package_manager/test_repos.py::test_pypi_mirror
Test procedure
  • Given Package Manager is running
  • When I query the PyPI repository for the "requests" package
  • Then the package is found in the repository
SKIPBioconductor mirror is accessible
tests/package_manager/test_repos.py::test_bioconductor_mirror
Test procedure
  • Given Package Manager is running
  • When I query the Bioconductor repository for the "BiocGenerics" package
  • Then the package is found in the repository
PASSAt least one repository is configured
tests/package_manager/test_repos.py::test_repo_exists
Test procedure
  • Given Package Manager is running
  • When I list all repositories
  • Then at least one repository exists

Prerequisites

4 tests — 2 passed, 1 failed, 1 skipped

PASS<product> server is reachable
tests/prerequisites/test_components.py::test_product_server_is_reachable[Connect]
Test procedure
  • Given <product> is configured in vip.toml
  • When I request the <product> health endpoint
  • Then the server responds with a successful status code
SKIP<product> server is reachable
tests/prerequisites/test_components.py::test_product_server_is_reachable[Workbench]
Test procedure
  • Given <product> is configured in vip.toml
  • When I request the <product> health endpoint
  • Then the server responds with a successful status code
PASS<product> server is reachable
tests/prerequisites/test_components.py::test_product_server_is_reachable[Package Manager]
Test procedure
  • Given <product> is configured in vip.toml
  • When I request the <product> health endpoint
  • Then the server responds with a successful status code
FAILWorkbench server is reachable but not configured
tests/prerequisites/test_expected_failure.py::test_workbench_expected_failure
Test procedure
  • Given Workbench is expected to be configured
  • When I check the Workbench configuration
  • Then Workbench should be reachable

Failed Tests

tests/prerequisites/test_expected_failure.py::test_workbench_expected_failure

What was tested: Workbench server is reachable but not configured — As a VIP developer I want to see what a failed test looks like in the report So that I can verify the report renders failures correctly

Error traceback
fixturefunc = <function workbench_reachable at 0x7f785fbd3560>
request = <FixtureRequest for <Function test_workbench_expected_failure>>
kwargs = {'wb_configured': False}

    def call_fixture_func(
        fixturefunc: _FixtureFunc[FixtureValue], request: FixtureRequest, kwargs
    ) -> FixtureValue:
        if inspect.isgeneratorfunction(fixturefunc):
            fixturefunc = cast(Callable[..., Generator[FixtureValue]], fixturefunc)
            generator = fixturefunc(**kwargs)
            try:
                fixture_result = next(generator)
            except StopIteration:
                raise ValueError(f"{request.fixturename} did not yield a value") from None
            finalizer = functools.partial(_teardown_yield_fixture, fixturefunc, generator)
            request.addfinalizer(finalizer)
        else:
            fixturefunc = cast(Callable[..., FixtureValue], fixturefunc)
>           fixture_result = fixturefunc(**kwargs)
                             ^^^^^^^^^^^^^^^^^^^^^

.venv/lib/python3.13/site-packages/_pytest/fixtures.py:915: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

wb_configured = False

    @then("Workbench should be reachable")
    def workbench_reachable(wb_configured):
>       assert wb_configured, (
            "Workbench is not configured. "
            "This is an expected failure used to demonstrate report rendering. "
            "Set [workbench] url in vip.toml to resolve."
        )
E       AssertionError: Workbench is not configured. This is an expected failure used to demonstrate report rendering. Set [workbench] url in vip.toml to resolve.
E       assert False

tests/prerequisites/test_expected_failure.py:42: AssertionError
Likely causes:
  • Workbench is not configured in vip.toml (expected in CI preview)
  • This test intentionally fails to demonstrate report failure rendering
Suggested next steps:
  1. No action needed — this failure is expected in the CI report preview
  2. To resolve, add a [workbench] section with a valid URL to vip.toml

Documentation: https://github.com/posit-dev/vip/issues/73

failures.json is written by pytest alongside results.json.