summaryrefslogtreecommitdiffstats
path: root/features/electrum.feature
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'origin/stable' into ↵test/10777-robust-boot-menu-with-more-fragile-testsintrigeri2016-08-241-0/+2
|\ | | | | | | test/10777-robust-boot-menu-with-more-fragile-tests
| * Test suite: mark one Electrum test as fragile.intrigeri2016-08-231-0/+1
| | | | | | | | refs: #11697
* | Cherry-pick commit 1bf50e3ccbf68a262d35b8472375ad9fdc29e7fc:intrigeri2016-07-271-2/+0
|/ | | | | | | | | | | | | | | | | | Unmark all scenarios that use Tails Installer as fragile. bugfix/11590-installer-robustness was based on this branch (bugfix/10720-installer-freezes-on-jenkins), and flagged the tests as fragile again, so we have to revert that on this branch so these tests run on Jenkins again. This branch is only meant to run more tests in Jenkins involving the boot menu for Refs: #10777 anyway, it won't be merged. This reverts the following commits: 3c02ea74788cffe0b4db21181f46778eab0689b5 20d07239a8e2c3706827edcf3b17266899c37a64 2c4c6434c0c6bdcf2534f966434bf92230af3698
* Optimize scenario by not using the network.anonym2016-06-011-1/+1
| | | | | | | | | | | Here we don't exercise any functionality that is affected by networking, so let's kill the delay (waiting for Tor to bootstrap) that enabling networking introduces. For general performance, but also since we just removed the @fragile tag from this scenario without a review'n'merge (or much testing); let's at least avoid introducing a dependency on (historically unreliable) Tor bootstrapping to Jenkins.
* Move feature-wide @fragile tag to the only affected scenario.anonym2016-06-011-2/+3
| | | | | Let's just hope that the untagged scenario isn't in fact fragile for some *other* reason.
* Revert "Flag online scenarios as fragile."intrigeri2016-02-201-1/+0
| | | | This reverts commit f8e5fb99e9a1747746b613f12d528f2fe5aeb06c.
* Give a more thoughtful name for the disk used by our snapshots.anonym2016-01-191-1/+1
| | | | | | | Hopefully a test writer would think twice before re-using this name when creating a new disk, so we won't repeat #10907. Refs: #10907
* Make sure Electrum connects before the restart.anonym2016-01-071-0/+1
| | | | This reflects actual usage better.
* Mark as fragile all tests that rely on Tails Installer.intrigeri2015-12-071-0/+1
| | | | Refs: #10720
* Flag online scenarios as fragile.bertagaz2015-12-071-0/+1
| | | | | They all rely on the `wait_until_tor_is_working` helper which has lately proven to be still buggy. That's tracked by ticket #10497.
* Mark the whole electrum.feature as @fragile.anonym2015-11-061-1/+1
| | | | See #10475.
* Improve names of generated snapshot restoring steps.anonym2015-10-061-2/+2
| | | | | | | | | Essentially I did: sed -i 's/Tails has booted/I have started Tails/' -- \ features/*.feature features/step_definitions/snapshots.rb (although there was a false positive that I had to restore)
* Fix gherkin causality term.anonym2015-10-021-1/+1
|
* Fix typo.anonym2015-08-141-1/+1
|
* Add new snapshot for when having logged in with persistence enabled.anonym2015-08-131-3/+1
| | | | | Most of the time when testing persistence, this is what we need so it will save some time and make the scenarios simpler.
* Also use a default persistence password instead of step parameter.anonym2015-05-151-2/+2
|
* Convert electrum.feature to the new snapshot model.anonym2015-05-151-14/+9
|
* Add Electrum test featurekytv2015-05-111-0/+38
This feature will test that * Electrum will display a warning message if Electrum is not persistent * creating a wallet will work * persistence for Electrum works Will-fix: #8963