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

Jul19 manual release tests: win10 py3qt5 #959

Closed
mrosanes opened this issue Jul 23, 2019 · 14 comments
Closed

Jul19 manual release tests: win10 py3qt5 #959

mrosanes opened this issue Jul 23, 2019 · 14 comments
Labels
tests windows this issue affects specifically to windows systems
Milestone

Comments

@mrosanes
Copy link
Collaborator

mrosanes commented Jul 23, 2019

This issue is created for reporting the results of the manual tests for Jul19 release on windows 10 with python3 and qt5.

Using a clean windows10 machine (provisioned with vagrant: taurus-vagrant). Using Conda environment py3qt5 (conda activate py3qt5), from inside the vagrant VM.

Using tar.gz from appveyor at commit 62bdfdb (from develop branch).

--

Note: only some tests were performed. Not tested qwt5 related checks (since it is not available for py3)

Note2: used TANGO_HOST controls05, because using controls01 (Tango7) problems with API_EventTimeout appeared: maybe to be changed in taurus-vagrant Readme. (Even disabling firewall, I got the API_EventTimeouts, when using controls01).

@mrosanes mrosanes added tests windows this issue affects specifically to windows systems labels Jul 23, 2019
@mrosanes mrosanes added this to the Jul19 milestone Jul 23, 2019
@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

Installation

For tips on how to prepare an environment for installation, see

  • Install Taurus from the an artifact of Appveyor (tgz or msi): pip install <tarball_artifact_URL>
  • Install taurus-pyqtgraph from the master branch of its repo:
    pip install https://github.com/taurus-org/taurus_pyqtgraph/archive/master.zip.
  • Check installed version of taurus: taurus --version
  • Check installed version of taurus_pyqtgraph: taurus tpg --version

taurus demo

  • Execute taurus demo
  • Test all of the buttons of the taurus demo. 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.unit", eval:10*arange(9)#rvalue[3:4])
  • For LCD: Test the foreground roles and the background role
    Errors found in the anaconda prompt. Issue Exception on stress test for setModel  #967
    https://gist.github.com/mrosanes/9066bd71aee4a6a510f7753a1d4fca4e
  • For Led: Test the colors, ON color, Off color. (hint: you can use eval:False as a model for testing)
    • Issue: taurus demo: Led  #972 NOT-A-BUG (~~@cpascual 20190725 see taurus demo: Led  #972 (comment))
    • Other problem for Led? Blue color never changes for sys/tg_test/1/state (even if the chosen color for the Led is another: rvalue always blue, quality always green) NOT-A-BUG This is the expected behaviour for a state value. The colormap in this case is the one for devstates (~cpascual 20190723)

Bug #709 is present when closing applications.

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus guiqwt image

  • Execute taurus guiqwt image --demo
  • try to resize the image and pan it using the mouse.
  • check the cross section tools, the color maps, etc.
    Cross sections and ROIs can be added but not removed, the image becomes full of crosses if adding more and more: maybe only one cross (or ROI) should be kept. NOT A BUG Actually they can be removed but it is not intuitive (go to item list, select the item and click on remove). In any case, this is the standard interface from guiqwt, not something we implemented in Taurus.
  • replace the image using the "Change Taurus Model" button (choose , eg, sys/tg_test/1/double_image_ro)

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus guiqwt trend2d

  • Execute: taurus --polling-period 333 guiqwt trend2d --demo
  • Execute: taurus --polling-period 333 guiqwt trend2d -xt --demo (known to fail in 4.1.0). Issue TaurusTrend2D fails when using absolute time scale #505
    TypeError: QwtScaleDiv() takes 0, 2, 3 or 5 argument(s) (4 given)
  • Execute: taurus --polling-period 333 guiqwt trend2d -xe --demo
  • Test auto-scroll and auto-scale tools (from context menu)
  • Test Save & restore config (change axes range, zoom, tool status colormap etc & check that everything is restored)
    Config cannot be saved; only an image .png can be saved
    ~~KNOWN ISSUE: you are right: this is reported in create Tool for saving/loading config in guiqwt widgets #239 . I just removed this check to avoid future confusion (@cpascual 20190723)

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus designer

  • Execute taurus designer. Check that the taurus widgets are present in the catalog
    taurus widgets are not present in taurus designer: Issue taurus widgets not present in 'taurus designer' #968 FIXED in release branch
  • Create an empty widget and drag various taurus widgets to it (they should be correctly dropped)

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus device

  • Execute: taurus device sys/tg_test/1
  • Check that it opens correctly and that the attrs and commands are populated
    Issue [Win] Dialogs launched with TaurusLauncherButton in a TaurusForm cannot be closed  #969: The images and tables opened with the buttons cannot be closed (with the cross)
  • 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)

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus panel

  • Execute: taurus panel
  • Navigate in the tree and select the TangoTest device (the attr an command panels should be populated)
  • Execute SwitchStates command to put it in FAULT, close the GUI and reopen it. Repeat previous point again.

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus config

  • Open an ini file with taurus config and check that it is loaded correctly.
    Popup: "No module named 'PyQt4", when trying to 'taurus config tgconf_macrogui.ini', from C:\Miniconda\envs\py3qt5\Lib\site-packages\taurus\qt\qtgui\taurusgui\conf\tgconf_macrogui EXPECTED BEHAVIOUR ... this is due to attempting to open an ini file created with PyQt4 using PyQt5. Not sure that we should bother about it... (~~@cpascual 20190723)

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus icons catalog

  • Launch taurus icons. 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.

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus form

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

  • Launch taurus form 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 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)
    It crashes: 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
    Issue [Win] Dialogs launched with TaurusLauncherButton in a TaurusForm cannot be closed  #969: The images and arrays cannot be closed with the cross once they have been opened
  • 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)
    Issue Forms use TaurusArrayEditor even when Qwt5 is not available #973 FIXED in release branch (~~@cpascual 20190725)
  • Change the write widget of double_scalar by a TaurusWheelEdit
  • Change other read and write widgets
  • After the previous changes, you should have a quite "custom" form. Use "Save current Settings" and save
    to "tf.pck". Close the form and reopen it with taurus form --config tf.pck
  • ... other features from user's guide

@cpascual cpascual mentioned this issue Jul 23, 2019
5 tasks
@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 23, 2019

taurus gui

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

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 24, 2019

taurus tpg plot (needs taurus_pyqtgraph installed)

  • Execute: taurus tpg plot "eval:Q(rand(333),'mm')" sys/tg_test/1/wave
  • Check zoom / panning (drag with right / left button), and Use (A) button to auto-range
  • Test inspector tool
  • Move curves between axes by using the plot configuration option in context menu
  • With curves in Y1 and Y2, test zooms and panning on separate axes (drag with right/left on the axis)
  • Test plot configuration dialog
  • Test changing curve titles
    Issue taurus tpg plot: curve names in legend cannot be changed taurus_pyqtgraph#31: even if applying, the curve titles are not changed in the legend NOT YET READY in pyqtgraph
  • Open the "Model Selection" (previous Model XY Chooser) dialog and add/remove/reorder/edit models. Try adding models both for X and Y
    - 'Model XY chooser' in the menu of tpg should be called 'Model selection' (in 'taurus tpg plot' and also in 'taurus tpg trend' FIXED with Rename option to 'Model selection' taurus_pyqtgraph#33
    - Issue (Win py3qt5) taurus tpg plot: missing options and icons inside 'Model Selection' taurus_pyqtgraph#35: Missing icons in Windows for: adding / removing all/ reordering up / reordering down
  • NOT YET READY Test Save & restore config (change curve properties, zoom, etc & check that everything is restored)

The application crashes at exiting (as most of Taurus applications in windows)

@mrosanes
Copy link
Collaborator Author

mrosanes commented Jul 25, 2019

taurus tpg trend (needs taurus_pyqtgraph installed)

  • Execute: taurus tpg trend "eval:Q(rand(),'mm')" sys/tg_test/1/ampli
  • Execute: taurus tpg trend "eval:Q(rand(),'mm')"
  • Execute: taurus tpg trend -xe "eval:Q(rand(),'mm')" sys/tg_test/1/ampli
    Issue Add options -x and -e in 'taurus tpg trend' taurus_pyqtgraph#27: Option -xe is not included in 'taurus tpg trend'; it should be included NOT YET READY (tpg.Trend does not yet support non-date x axis)(~~@cpascual 20190725)
  • Check zoom / panning (drag with right / left button), and Use (A) button to auto-range
  • Test inspector tool
  • Added test: Right click menu -> plot options -> transforms -> Power Spectrum
    Issue Power Spectrum option bug taurus_pyqtgraph#30 Not our bug. This is a bug in pyqtgraph which has already been fixed, but is only available in the unreleased development code (~~@cpascual 20190725)
  • Move curves between axes by using the plot configuration option in context menu
  • With curves in Y1 and Y2, test zooms and panning on separate axes (drag with right/left on the axis)
  • Test plot configuration dialog
  • Test Forced reading tool
  • Test X Axis 'fixed range scale' mode (autopanning)
  • Test autoscale x mode
  • NOT YET READY Test Save & restore config (change curve properties, zoom, etc & check that everything is restored)

@mrosanes
Copy link
Collaborator Author

Output of automatic tests (taurus testsuite) for Win10 py3qt5:
https://gist.github.com/mrosanes/5a4cafb3d5c4458ab1e54453f3714bda

@cpascual
Copy link
Member

All relevant issues found have been already fixed and/or reported in the tracker, and none is considered release-critical. I am closing this test issue. Thanks @mrosanes for the tests!

@cpascual cpascual mentioned this issue Jul 14, 2020
3 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tests windows this issue affects specifically to windows systems
Projects
None yet
Development

No branches or pull requests

2 participants