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 Inelastic interfaces #37986

Closed
MohamedAlmaki opened this issue Sep 17, 2024 · 15 comments
Closed

Manual Testing Inelastic interfaces #37986

MohamedAlmaki opened this issue Sep 17, 2024 · 15 comments
Assignees
Labels
Manual Tests Only for issues that are unscripted testing tasks during the release period
Milestone

Comments

@MohamedAlmaki
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:

Follow the directions at:

@MohamedAlmaki MohamedAlmaki added the Manual Tests Only for issues that are unscripted testing tasks during the release period label Sep 17, 2024
@MohamedAlmaki MohamedAlmaki added this to the Release 6.11 milestone Sep 17, 2024
@cailafinn
Copy link
Contributor

cailafinn commented Sep 19, 2024

On Quasi Tab, have 50 spectra in output rather than 9.

Never mind, this happens if you use the SampleData-ISIS instead of the Usage data.

@cailafinn
Copy link
Contributor

cailafinn commented Sep 19, 2024

Deprecation warning when running on Quasi tab:

This algorithm is deprecated, please use BayesQuasi2 instead.

@warunawickramasingha
Copy link
Contributor

warunawickramasingha commented Sep 19, 2024

Quasi Tab step 12: the titles of the plots do not reflect what is being plotted as to whether Prob, Amplitude and FWHM

@warunawickramasingha
Copy link
Contributor

warunawickramasingha commented Sep 19, 2024

Stretch Tab step 12. It only opens two plots, not three plots

@warunawickramasingha
Copy link
Contributor

warunawickramasingha commented Sep 19, 2024

Container Subtraction tab step:7 "This should plot a blue corrected line"

@cailafinn
Copy link
Contributor

cailafinn commented Sep 19, 2024

Crash in Symmetrise Tab when:

  1. Data is loaded
  2. ADS is cleared
  3. Preview button is pressed

THIS IS A REGRESSION. Not present in 6.10, should be fixed for 6.11.
Seen on macOS and IDAaaS.

@warunawickramasingha
Copy link
Contributor

warunawickramasingha commented Sep 19, 2024

Symmetrise tab step 19: instruction need to be updated to "On Spectrum Numbers select 5"

@RichardWaiteSTFC
Copy link
Contributor

On Moments tab
After final step of Plot Spectra, the line edit is disabled and subsequent plots with different spectrum indices cannot be made unless you click Run again

@warunawickramasingha
Copy link
Contributor

On Moments tab After final step of Plot Spectra, the line edit is disabled and subsequent plots with different spectrum indices cannot be made unless you click Run again

This is Not a regression.

@warunawickramasingha
Copy link
Contributor

Crash in Symmetrise Tab when:

  1. Data is loaded
  2. ADS is cleared
  3. Preview button is pressed

THIS IS A REGRESSION. Not present in 6.10, should be fixed for 6.11. Seen on macOS and IDAaaS.

#38042 was raised!

@yusufjimoh
Copy link
Contributor

Incorrect plot label for on Quasi and Stretch Tab
#38043 has been created for it

@warunawickramasingha
Copy link
Contributor

#38064 was raised to update test instructions as mentioned above

@warunawickramasingha
Copy link
Contributor

On Moments tab After final step of Plot Spectra, the line edit is disabled and subsequent plots with different spectrum indices cannot be made unless you click Run again

#38065 was raised

@warunawickramasingha
Copy link
Contributor

Deprecation warning when running on Quasi tab:

This algorithm is deprecated, please use BayesQuasi2 instead.

#38066 was raised

@warunawickramasingha
Copy link
Contributor

Test time~1h and 50mints

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

7 participants