Skip to content
This repository has been archived by the owner on Mar 17, 2021. It is now read-only.

Test 'support for python3' code in debian9 + python2 at ALBA #816

Closed
80 of 85 tasks
cpascual opened this issue Oct 8, 2018 · 3 comments
Closed
80 of 85 tasks

Test 'support for python3' code in debian9 + python2 at ALBA #816

cpascual opened this issue Oct 8, 2018 · 3 comments
Labels

Comments

@cpascual
Copy link
Member

cpascual commented Oct 8, 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

  • Install Taurus from the tar.gz : 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

  • Test all of the buttons of the taurusdemo. All demos should launch correctly and without raising exceptions
  • For TaurusLabel, check foreground role, the background role, the prefix, the suffix, the formatter, etc.
  • For TaurusLabel, in order to test the background role=value, you can use the following attribute: eval:["FAULT","ON","OFF","ALARM"][randint(4)]
  • For TaurusLabel, use a model with fragment (e.g., sys/tg_test/1/ampli#rvalue.magnitude, eval:Q('1mm')#rvalue.units", eval:10*arange(9)#rvalue[3:4])
  • For LCD: Test the foreground roles and the background role
  • For Led: Test the colors, ON color, Off color. (hint: you can use eval:False as a model for testing)

taurusplot

(basically try all features described in the user's guide

  • Execute: taurusplot "eval:Q(rand(333),'mm')" sys/tg_test/1/wave
  • Check region Zoom in and out with region zoom and go back stacked zoom levels with the mouse middle button
  • Check mouse wheel Zoom
  • Test panning (dragging with CTRL pressed)
  • Test inspector mode
  • Test pause mode
  • Move curves between axes by clicking on legend (and test zoom on Y2)
  • Test plot configuration dialog
  • Test changing curve titles
  • Test Save & restore config (change curve properties, zoom, etc & check that everything is restored)
  • Open the "Input data selection" dialog and add/remove/reorder /edit models
  • export one curve data to ASCII and then load it using "Input data selection" -> raw data -> open file
  • ... other features from user's guide

taurustrend

(basically try all features described in the user's guide

  • Execute: taurustrend "eval:Q(rand(),'mm')" sys/tg_test/1/ampli
  • Execute: taurustrend -xe "eval:Q(rand(),'mm')" sys/tg_test/1/ampli
  • Check region Zoom in and out with region zoom and go back stacked zoom levels with the mouse middle button
  • Check mouse wheel Zoom
  • Test panning (dragging with CTRL pressed)
  • Test inspector mode
  • Test pause mode
  • Move curves between axes by clicking on legend (and test zoom on Y2)
  • Test plot configuration dialog
  • Test Forced reading mode
  • Test autopanning mode
  • Test autoscale x mode
  • Test Save & restore config (change curve properties, zoom, etc & check that everything is restored)
  • ... other features from user's guide

Test taurusimage

  • Execute taurusimage --demo
  • try to resize the image and move it using the mouse.

taurustrend2d

  • Execute: taurustrend2d --demo --taurus-polling-period 333
  • Execute: taurustrend2d -xt --demo --taurus-polling-period 333 (known to fail in 4.1.0)
  • Execute: taurustrend2d -xe --demo --taurus-polling-period 333
  • Test auto-scroll and auto-scale tools
  • 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.
  • Test to drag and drop of this attribute onto the same form many times (4 times)
    (If it crashes, you are seeing bug TaurusForm crashes on windows if self-droping a model #96)
  • Open "Modify Contents" and add sys/tg_test/1 and all of its attributes. They should all show ok
  • Test the compact mode (switch to compact, noncompact; edit when in compact mode, ...) for a single
    value (from the context menu of a value label)
  • Test compact mode for all values (from the context menu of the whole form)
  • Test changing labels
  • Test changing the formatter for a single value (from the context menu of a value label) (use, e.g. >>{}<<). Do this in compact and non compact modes.
  • Test changing the formatter for all values (from the context menu of the whole form)
  • Test re-order of values with "Modify contents"
  • Test the different "show" buttons (tables, images, spectra)
  • Change the write widget of double_scalar by a TaurusWheelEdit
  • Change other read and write widgets
  • ... other features from user's guide

taurusgui

(basically try all features described in the user's guide

  • Launch taurusgui example01
  • Test (un)lock view
  • Create a new panel (a TaurusForm) and drag and drop several models from other forms
  • Move panels around (with view unlocked!) and hide ("close") and re-show them
  • Test saving and restoring perspectives
  • Test drag&drop from a form to a trend
  • Test clicking on "example01 synoptic" elements and check that the panels raised
  • Test that selecting a panel changes the selection on "example01 synoptic"
  • Test the actions in the menus
  • Create a new TaurusGui (call it foogui) with taurusgui --new-gui (follow the wizard)
  • Install foogui with pip (using a virtualenv may be a good idea)
  • launch foogui using the script that has been installed
  • ... other features from user's guide

taurusconfigbrowser

  • Open an ini file with taurusconfigbrowser and check that it is loaded correctly.

taurusiconcatalog

  • Launch taurusiconcatalog. Several tabs with an array of icons should be displayed
  • Check that tooltips give info on each icon
  • Click on some icons and check that they give a bigger view of the icon and more info.

sardana

@cpascual cpascual changed the title Manual tests for python3 support (debian-py2) Test 'support for python3' code in debian9 + python2 at ALBA Oct 10, 2018
@cpascual 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
@cpascual
Copy link
Member Author

cpascual commented Oct 11, 2018

While doing the tests I've found some issues that are not specific to #703 and which I reported directly to the taurus issue tracker: #821, #822

@cmft
Copy link
Member

cmft commented Oct 16, 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 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
@cpascual
Copy link
Member Author

All tests ok. Closing

@cpascual cpascual added the tests label Oct 19, 2018
@cpascual cpascual mentioned this issue Feb 11, 2019
3 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants