Hot answers tagged specflow
6
As a general rule of thumb, everytime a test fails or has an indeterminate outcome it requires investigation. If you ignore a failing/indeterminate test then you increase the risk of missing or overlooking a bug.
The value of automation is to execute tests that we deem important enough that we want to run them repeatitively, or tests that are executed more ...
2
If you are using SpecFlow look at the Tags Tags description where placing a specific tag before your Scenario allows you to run the specific ones you want. I use @test or @dev for specific User/Functional Tests and when using my NUnit Driver I put in the tag with the /include option. This links in to the SpecFlow feature files such that the following case ...
2
It appears that NUnit http://www.nunit.org/index.php?p=testFixture&r=2.5 now supports parameterized test fixtures. This may allow you to create a test that will do what you need. This SO answer has a similar question for NUnit selenium tests.
...
2
You certainly can. Both WebClient, or HttpRequest would work well as the 'glue' for this scenario.
Note that I'd probably rephrase your Given/When/Then Statement as something like:
Given the logon page at http://someurl/account/logon
When I post with parameters username='test' and password='123'
Then I am redirected to http://someurl/home
1
You can use Given/When/Then for scenarios with any complicity level, for instance,
Very specific scenario:
Scenario: Error when the password and confirm password do not match
Given I am on User Registration From
When I fill the Form fields as follow:
| Field | Value |
| Name | myusrname|
| Password| password123|
|Confirm Password | ...
1
The insertion of Thread.Sleep() is typically indicative of a race condition in your test and your test is running out of sync with the thing is it testing.
One suggestion may be to insert a polling loop to wait for the redirect, or an event to indicate the redirect has happened.
See http://www.testingmentor.com/imtesty/2012/06/11/sleepy-automated-tests/ ...
1
We also have same issue in our production monitoring automation suite. To solve this problem to some extent, whenever a test is failed it is marked as INTERMITTENT and same test is repeated for max. 3 times or until it is passed. If it is getting passed in any one of next repetition then issue is left as Intermittent and not alerted. If it is failing all the ...
Only top voted, non community-wiki answers of a minimum length are eligible
