You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.
Test Save & restore config (change axes range, zoom, tool status colormap etc & check that everything is restored)
taurusdesigner
Check that taurusdesigner is correctly opened and taurus widgets are present in the catalog
Create an empty widget and drag various taurus widgets to it (they should be correctly dropped)
taurusdevicepanel
Execute: taurusdevicepanel sys/tg_test/1
Check that it opens correctly and that the attrs and commands are populated
Execute SwitchStates command (see that the state label changes to FAULT and its color to red)
and then execute the Init command and the label returns to RUNNING (blue)
tauruspanel
Execute: tauruspanel
Navigate in the tree and select the TangoTest device (the attr an command panels should be populated)
taurusform
(basically try all features described in the user's guide
Launch taurusform sys/tg_test/1/short_scalar
go to label context menu, change the configuration and set range to (-1000, 1000), alarm to (-500, 500) and unit to mm. Close the form and relaunch. The new units should be used. Change the the write value and check that the orange color is used when in warning values, and that the write widget does not allow to write values out of range.
cpascual
changed the title
Test 'support for python3' code in debian9 + python2 at ALBA
[WIP] Test 'support for python3' code in debian9 + python2 at ALBA
Oct 11, 2018
I found troubles with taurusdesigner if you starting to create a GUI and you decided do not save it the designer does not died
cpascual
changed the title
[WIP] Test 'support for python3' code in debian9 + python2 at ALBA
Test 'support for python3' code in debian9 + python2 at ALBA
Oct 18, 2018
This issue is created for reporting the results of the manual tests for python 2 & 3 support PR #703
Tested on Debian GNU/Linux 9 (stretch) with python2 using the checklist from
https://github.com/taurus-org/taurus/blob/develop/doc/how_to_release.md#manual-test-checklist
Installation
pip install <tarball_artifact_URL>
pip install https://ci.appveyor.com/api/buildjobs/3kt2he6dq96t4fvw/artifacts/dist%2Ftaurus-4.4.1a0.tar.gz
pip install https://ci.appveyor.com/api/buildjobs/3espsq058vso149q/artifacts/dist%2Ftaurus-4.4.1a0.tar.gz
pip install https://ci.appveyor.com/api/buildjobs/vtagrjlwrnlyeltl/artifacts/dist%2Ftaurus-4.4.1a0.tar.gz
pip install https://ci.appveyor.com/api/buildjobs/24op01lxvitvsj58/artifacts/dist%2Ftaurus-4.4.1a0.tar.gz
pip install https://ci.appveyor.com/api/buildjobs/eyc0uubsvqy7ivfe/artifacts/dist%2Ftaurus-4.4.1a0.tar.gz
Taurusdemo
Problems found with taurusmessagebox and taurusmessagepanel: https://github.com/piertoni/taurus/issues/12FIXEDProblems found with label, lcd and led demos: https://github.com/piertoni/taurus/issues/13FIXEDeval:["FAULT","ON","OFF","ALARM"][randint(4)]
sys/tg_test/1/ampli#rvalue.magnitude
,eval:Q('1mm')#rvalue.units"
,eval:10*arange(9)#rvalue[3:4]
)eval:False
as a model for testing)taurusplot
(basically try all features described in the user's guide
taurusplot "eval:Q(rand(333),'mm')" sys/tg_test/1/wave
taurustrend
(basically try all features described in the user's guide
taurustrend "eval:Q(rand(),'mm')" sys/tg_test/1/ampli
taurustrend -xe "eval:Q(rand(),'mm')" sys/tg_test/1/ampli
Test taurusimage
taurusimage --demo
taurustrend2d
taurustrend2d --demo --taurus-polling-period 333
taurustrend2d -xt --demo --taurus-polling-period 333
(known to fail in 4.1.0)taurustrend2d -xe --demo --taurus-polling-period 333
taurusdesigner
taurusdevicepanel
taurusdevicepanel sys/tg_test/1
and then execute the Init command and the label returns to RUNNING (blue)
tauruspanel
tauruspanel
taurusform
(basically try all features described in the user's guide
taurusform sys/tg_test/1/short_scalar
mm
. Close the form and relaunch. The new units should be used. Change the the write value and check that the orange color is used when in warning values, and that the write widget does not allow to write values out of range.(If it crashes, you are seeing bug TaurusForm crashes on windows if self-droping a model #96)
value (from the context menu of a value label)
>>{}<<
). Do this in compact and non compact modes.taurusgui
(basically try all features described in the user's guide
taurusgui example01
foogui
) withtaurusgui --new-gui
(follow the wizard)foogui
with pip (using a virtualenv may be a good idea)foogui
using the script that has been installedtaurusconfigbrowser
taurusiconcatalog
taurusiconcatalog
. Several tabs with an array of icons should be displayedsardana
install latest sardana release ()
pip install sardana
on another console, run
Sardana demo1
launch spock and run sar_demo
in spock, run a couple of macros
lsm
,ascan mot01 1 10 9 .1
launch
sardanatestsuite
(I had to install a patchedlibtango9 9.2.5a+dfsg1-2+patch3~bpo9+0~alba+1
to avoid the bug from Set the ZMQ Receive Buffer High Water Mark only if it changes (#444) tango-controls/cppTango#445): Results:Ran 184 tests in 625.824s OK (skipped=7, expected failures=1)
create a gui with
taurusgui --new-gui
that connects to demo1 , install it and check that the macroexecutor and the other macro-related panels workI got a problem https://github.com/piertoni/taurus/issues/16FIXEDThe text was updated successfully, but these errors were encountered: