Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Manual Testing Mantid Basics Course #38641

Closed
Tracked by #38664
warunawickramasingha opened this issue Jan 21, 2025 · 10 comments
Closed
Tracked by #38664

Manual Testing Mantid Basics Course #38641

warunawickramasingha opened this issue Jan 21, 2025 · 10 comments
Assignees
Labels
Manual Tests Only for issues that are unscripted testing tasks during the release period
Milestone

Comments

@warunawickramasingha
Copy link
Contributor

You have been assigned manual testing. The hope is to catch as many problems with the code before release, so it would be great if you can take some time to give a serious test to your assigned area. Thank you!!

The general guide to manual testing:

  • The tests must be performed on the installer versions of the final release candidate. Not on local compiled code.
  • Serious errors involving loss of functionality, crashes etc. should be raised
    as issues with the current release as a milestone and an email sent to the project manager immediately.
  • Minor and cosmetic issues should be raised as issues against the forthcoming
    releases.
  • First try things that should work, then try to break Mantid, e.g. entering invalid values, unexpected characters etc.
  • Don't spend more than a few hours on the testing as fatigue will kick in.
  • If you find errors in the documentation, please correct them.
  • Comment against this ticket the OS environment you are testing against.
  • Disable Usage reporting before you start testing
  • Close the this issue once you are done.
  • Time how long this manual test takes for you to do and leave a comment about it in this issue.

Specific Notes:

@warunawickramasingha warunawickramasingha added the Manual Tests Only for issues that are unscripted testing tasks during the release period label Jan 21, 2025
@warunawickramasingha warunawickramasingha added this to the Release 6.12 milestone Jan 21, 2025
@adriazalvarez
Copy link
Contributor

Getting started page could update the documentation
https://docs.mantidproject.org/nightly/tutorials/mantid_basic_course/getting_started/getting_started.html#getting-started.
Version 6.12 has added a Move to Top button to the manage user directories, so it would be good to update it in this page.

Image

@rbauststfc
Copy link
Contributor

This screenshot of the Display Settings drop-down seems to be missing some options so could be updated.

@rbauststfc
Copy link
Contributor

rbauststfc commented Jan 21, 2025

Get the following unexpected exception on the Filter Events Interface:

Traceback (most recent call last): File "/opt/mantidworkbenchnightly/lib/python3.10/site-packages/mantidqtinterfaces/FilterEvents/eventFilterGUI.py", line 216, in callback sender_edit.callback() File "/opt/mantidworkbenchnightly/lib/python3.10/site-packages/mantidqtinterfaces/FilterEvents/eventFilterGUI.py", line 286, in set_startTime newtime0 = np.clip(inps, xlim[0], float(self.ui.leStopTime.text()))
ValueError: could not convert string to float: ''

Reproduce by:

  • Go to Interfaces -> Utility -> Filter Events.
  • Delete the entry in the Stopping Time field (under the plot). Leave the entry in the Starting Time field.
  • Put your cursor into the Starting Time field and hit enter on the keyboard.

Also works the other way around (i.e. clear Starting Time and hit enter in Stopping Time). The dialog seemed to change a bit in 6.10 and the issue was introduced then. Note that the screenshot here is also showing the old version of the interface and needs to be updated.

I've opened issue #38665 for this.

@rbauststfc
Copy link
Contributor

Some of the screenshots on this page need updating.

@rbauststfc
Copy link
Contributor

I've opened issue #38664 to capture updates to the course documentation.

@MohamedAlmaki
Copy link
Contributor

MohamedAlmaki commented Jan 22, 2025

The loading screenshot is missing clear here. Also, in workspace tool here

@MialLewis
Copy link
Contributor

MialLewis commented Jan 22, 2025

Displaying data page suggests using MUSR00015189 dataset.

When using the pick tab as per Investigating data, the unit of the x axis is label on the miniplot.

This causes an error to be thrown when using the Add a single crystal peak tool, which may confuse new users.

Is this wierd unit being caused by a regression?

Edit: This also effects selecting detector by tube/bank. If you change the miniplot from sum to integration, you can then change the x axis to a correct unit, which allows the selection function to work correctly.

@MialLewis
Copy link
Contributor

When selecting multiple detectors using a drawn shape, are we expecting to see any details in the selection box?

@rbauststfc
Copy link
Contributor

When selecting multiple detectors using a drawn shape, are we expecting to see any details in the selection box?

If I try doing this in 6.9 then there don't seem to be any details either.

@MialLewis
Copy link
Contributor

This is now finished from my perspective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Manual Tests Only for issues that are unscripted testing tasks during the release period
Projects
None yet
Development

No branches or pull requests

5 participants