# test of Catalyst installation not working

**URL:** https://discourse.paraview.org/t/test-of-catalyst-installation-not-working/3643
**Category:** In Situ Support
**Created:** [February 24, 2020, 9:06am UTC](https://discourse.paraview.org/t/test-of-catalyst-installation-not-working/3643 "2020-02-24T09:06:46Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Rigel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@Rigel](https://discourse.paraview.org/u/Rigel)
#### Post date: [February 24, 2020, 9:06am UTC](https://discourse.paraview.org/t/test-of-catalyst-installation-not-working/3643/1 "2020-02-24T09:06:46Z")

</div>

Hi,

I am having problems to connect live to a simulation through Catalyst. Searching in this forum, I found

> [@Catalyst live visualization](https://discourse.paraview.org/t/catalyst-live-visualization/967/6):
>
> Take a look at the ParaView tests that exercise this functionality: [~/projects/ParaView/build]$ ctest -R CatalystLive Test project /home/danlipsa/projects/ParaView/build Start 1848: pv.CatalystLiveSetBreakpoint 1/4 Test #1848: pv.CatalystLiveSetBreakpoint … Passed 29.40 sec Start 1849: pvcs.CatalystLiveSetBreakpoint 2/4 Test #1849: pvcs.CatalystLiveSetBreakpoint … Passed 29.10 sec Start 1850: pv.CatalystLivePause 3/4 Test #1850: pv.CatalystLivePause … Passed 33.21 sec Start…

and decided to try @danlipsa 's suggestion about running `ctest -N -V -R CatalystLive` from the build directory, but that’s everything I get as a result:

```
alves@tauruslogin4:/lustre/ssd/ws/alves-paraview/v5.7.0/build> ctest -N -V -R CatalystLive
UpdateCTestConfiguration from :/lustre/ssd/ws/alves-paraview/v5.7.0/build/DartConfiguration.tcl
Parse Config file:/lustre/ssd/ws/alves-paraview/v5.7.0/build/DartConfiguration.tcl
 Add coverage exclude regular expressions.
 Add coverage exclude: vtk[^\.]+(Java|Python).cxx
 Add coverage exclude: .*Testing.Cxx.*cxx
 Add coverage exclude: .*Testing.Cxx.*h
 Add coverage exclude: .*moc_.*cxx
 Add coverage exclude: .*/Utilities/.*
 Add coverage exclude: .*/ThirdParty/.*
 Add coverage exclude: .*/VTK/.*
 Add coverage exclude: vtk[^\.]+ClientServer.cxx
 Add coverage exclude: vtk[^\.]+Python.cxx
 Add coverage exclude: ui_[^\.]+.h
 Add coverage exclude: moc_[^\.]+.h
 Add coverage exclude: vtkprotobuf
SetCTestConfiguration:CMakeCommand:/software/haswell/CMake/3.12.1-GCCcore-6.4.0/bin/cmake
UpdateCTestConfiguration from :/lustre/ssd/ws/alves-paraview/v5.7.0/build/DartConfiguration.tcl
Parse Config file:/lustre/ssd/ws/alves-paraview/v5.7.0/build/DartConfiguration.tcl
Test project /lustre/ssd/ws/alves-paraview/v5.7.0/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements

Total Tests: 0

```

ParaView (version 5.7.0) was built with `BUILD_TESTING:BOOL=ON`, so I don’t understand why I cannot see the tests outputs. [CMakeCache.txt](https://discourse.paraview.org/uploads/short-url/l1WZy5D8WUcmPBEKjtKir3oz3Yf.txt) (294.7 KB) is attached. Could you help me?

Thank you very much,

---

<div class="post-metadata">

### Author: ![Rigel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/r/8e7dd6/32.png) [@Rigel](https://discourse.paraview.org/u/Rigel)
#### Post date: [February 25, 2020, 12:04pm UTC](https://discourse.paraview.org/t/test-of-catalyst-installation-not-working/3643/2 "2020-02-25T12:04:51Z")

</div>

The build-time variable is not called `BUILD_TESTING` (anymore), but `PARAVIEW_BUILD_TESTING`. Also there is no `CatalystLive` test (anymore).

---

<div class="post-metadata">

### Author: ![utkarsh.ayachit](https://discourse.paraview.org/user_avatar/discourse.paraview.org/utkarsh.ayachit/32/39_2.png) [@utkarsh.ayachit](https://discourse.paraview.org/u/utkarsh.ayachit)
#### Post date: [February 25, 2020, 3:50pm UTC](https://discourse.paraview.org/t/test-of-catalyst-installation-not-working/3643/3 "2020-02-25T15:50:14Z")

</div>

See this: [https://gitlab.kitware.com/paraview/paraview/issues/19611](https://gitlab.kitware.com/paraview/paraview/issues/19611)

They were indeed accidentally removed and need to be brought back.
