Specflow bypasses subsequent scenarios after a failure -


all scenarios supposed but, until now, had 1.

now have second scenario, following problem arises.

if scenario 1 fails assertion, subsequent scenarios skipped.

see below skipped scenarios.

setup: configfiletransformation (thread #0) scenario: shows telephone numbers on header in showcontactinformation     (target: browserbrowserstack_win8_chrome_52) -> succeeded on thread #0 scenario: shows telephone numbers on contact sidebar box in     showcontactinformation (target: browserbrowserstack_win8_chrome_52)     -> failed on thread #0     [error] 2 assertions failed. restore: configfiletransformation (thread #0) scenario: shows telephone numbers on header in showcontactinformation     (target: browserbrowserstack_win8_firefox_42)     -> skipped on thread #-1 scenario: shows telephone numbers on contact sidebar box in     showcontactinformation     (target: browserbrowserstack_win8_firefox_42)     -> skipped on thread #-1 result: 1 failed   total: 4   succeeded: 1   ignored: 0   pending: 0   skipped: 2 <--- **** other scenarios must executed regardless of else.   failed: 1

how prevent specflow skipping subsequent scenarios?

updated execution element of test profile to:

<execution retryfor="none" stopafterfailures="0" testthreadcount="1" testschedulingmode="sequential" />

the key thing seems stopafterfailures="0".


Comments

Post a Comment

Popular posts from this blog

asynchronous - C# WinSCP .NET assembly: How to upload multiple files asynchronously -

i using winscp .net assembly uploading files. want upload multiple files asynchronous way. have created method works single upload. public class uploadingdata { private sessionoptions _sessionoptions; private session _session; //connection etc private void onconnected() { foreach (var fileinfo in localfileslist) { var task = task.factory.startnew(() => uploadfilesasync(fileinfo)); } } private async task uploadfilesasync(string file) { string remotefilepath = _session.translatelocalpathtoremote(file, @"/", "/test_data_upload"); var uploading = _session.putfiles(file, remotefilepath, false); //when done await task.run(() => thread.sleep(1000)); } } please suggest me correct way. thanks you can use backgroundworker class this: string[] images = new string[50]; foreach (var path in images) { backgroundworker
Read more

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

i getting "__type": "com.amazon.coral.service#serializationexception" as reply in postman & in test console in api gateway trying post record directly dynamodb using api proxy services.. referring aws article - https://aws.amazon.com/blogs/compute/using-amazon-api-gateway-as-a-proxy-for-dynamodb/ here's mapping { "tablename": "tablenamegoeshere", "item": { "id" : "$context.requestid" "eventname" : "$input.path('$.eventname')", "timestamp" : $input.path('$.timestamp'), "answers": "$util.parsejson($input.path('$.answers'))" } } update: did asked ... , worked if try add array of json objects gives me above same error - here's trying now. please - couldnt find on google well #set($inputroot = $input.path('$')) { "tablename": "answer", "item": {
Read more

asp.net - Problems sending emails from forum -

i have been redesigning site has message board, has been written guy looked after site. it has few problems , written in .asp , uses .mdb files database. you can see whole thing here . feel free post if helps, test thing have set using original files , new database. the basic problem when posts message, supposed email sent them, have posted it. when replies, originator supposed message, replier has been posted. i’d have thought @ point in process there should script/file in postmessage.asp? the postmessage.asp page below. <% option explicit %> <!-- #include virtual="common/adovbs.inc" --> <html> <head> <meta http-equiv="content-type" content="text/html; charset=windows-1252"> <meta name="generator" content="microsoft frontpage 4.0"> <meta name="progid" content="frontpage.editor.document"> <title>new page 2</title> <base target="_self"
Read more