Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
mantid
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Locked files
Deploy
Releases
Model registry
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
mantidproject
mantid
Commits
11717db7
Commit
11717db7
authored
6 years ago
by
Keith Butler
Browse files
Options
Downloads
Patches
Plain Diff
Re #23570 updating unscripted tests
parent
4de382fa
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
dev-docs/source/Testing/ErrorReporter-ProjectRecovery/ProjectRecoveryTesting.rst
+8
-8
8 additions, 8 deletions
.../ErrorReporter-ProjectRecovery/ProjectRecoveryTesting.rst
with
8 additions
and
8 deletions
dev-docs/source/Testing/ErrorReporter-ProjectRecovery/ProjectRecoveryTesting.rst
+
8
−
8
View file @
11717db7
...
...
@@ -24,9 +24,9 @@ Project Recovery test
--------------
1. Simple tests
and Muon-esque workflow
1. Simple tests
- Open MantidPlot
- make sure no other instances of MantidPlot are running
- Open MantidPlot
- Right-click in the Results Log and set `Log level` to `Debug`
- The Results Log should be printing `Nothing to save`
- Run the following command to create a simple workspace:
...
...
@@ -75,7 +75,7 @@ Project Recovery test
2. Testing many workspaces
- Open up MantidPlot
, ensure that it is the only instance running
- Open up MantidPlot
- Run the following script:
.. code-block:: python
...
...
@@ -106,7 +106,7 @@ Project Recovery test
3. Testing workspaces of different types
- Open up MantidPlot
, ensure that only one instance is running
- Open up MantidPlot
- Run the following script:
.. code-block:: python
...
...
@@ -207,7 +207,7 @@ Project Recovery test
6. Opening script only
- Open MantidPlot
- make sure no other instances of MantidPlot are running
- Open MantidPlot
- Run the second script from test 1
- In the workspace window right-click the ``Sequential3`` workspace and choose `Plot spectrum`
- Choose `Plot All`
...
...
@@ -222,14 +222,14 @@ Project Recovery test
7. Not attempting recovery
- Open MantidPlot
- make sure no other instances of MantidPlot are running
- Open MantidPlot
- Run the second script from test 1
- In the workspace window right-click the ``Sequential3`` workspace and choose `Plot spectrum`
- Choose `Plot All`
- Crash Mantid with `Segfault` from the algorithm window
- Reopen Mantid
- You should be presented with the Project Recovery dialog
- Choose `
No
`
- Choose `
Start mantid normally
`
- Mantid should open as normal
- With the Results Log in debug level you should see the project saver starting up again
...
...
@@ -237,7 +237,7 @@ Project Recovery test
8. Check old history is purged
- Open MantidPlot
- make sure no other instances of MantidPlot are running
- Open MantidPlot
.. code-block:: python
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment