nunit | testing framework | Unit Testing library

The observable Zip operator works just the same as the enumerable version. You didn't use that in the first test so it's not like to be the operator you need here.

What you need is simply the SelectMany operator.

Try this query:

When you setup without any code - that method does nothing, but you need it to call your action. Try this:

You need to split the string on the newline character (\n). One way to do that is the .split() method, which returns a list of strings split on a given string. For example:

Thanks for contacting Syncfusion support.

We have checked the code example provided and identified that “await ImageDownloader.downloadImage(url)” returns null. Due to this, there is no image preserved in PDF grid cell. We have created a sample to read the image data from webspace/website and drawn the image using the retrieved image data. Kindly try the following code example and sample in your side and let us know whether the issue is resolved at your end.

1. Add http package in dependencies section of pubspec.yaml file

You can add all progress reports to a list then do the asserts on the collection. The number of items will be equal to the number of progress reports and in the same order. You can check any number of conditions related to progress report.

About your tests failing, this is odd because if they ran correctly then they should have the same result each time you ran them because there is no dependency on state. The only dependency is on the test runner actually running async tests. NUnit should be able to do that, as far as I know it has support for async tests.

The Progress instance captures the current SynchronizationContext and runs the callback using it. This is particularly useful for UI because the progress callback will be executed on the UI thread so you don't need to worry about that. It is likely that NUnit has its own custom SynchronizationContext for executing async tests and your tests sometimes failing and sometimes not may be related to progress reports being executed after the related test has actually finished. In this case, you may actually get the assert exception of one test on a different test.

If this is true, then you may need to have your own implementation of IProgress that does not use the SynchronizationContext in order to properly have the progress reports executed. Basically what you want is to have your callback executed when you call the report method. Your implementation can do exactly that, whenever you call the progress method it will add the reported value to a list, that is exposed through a property, and then do the asserts using the property.

What is giving you your strange results is most likely the usage of the Progress class as it internally depends on the SynchronizationContext to execute the callback.

Found solution/reason: The Problem is that after slice process the test case filter isn't working, solution was the rename to “TestCategory”, before it was “Category“ for TestCaseFilter – Lukas Windner May 21 at

Well, finally solved! It was a workaround between NUnit and TransactionScope. Testing an async method that hits the database using a TransactionScope (to keep the database clean) causes a timeout exception when executing the command.

The way to solve this issue was: upgrade to NET Framework 4.5.1 and add TransactionScopeAsyncFlowOption.Enabled to the TransactionScope constructor.

Setup attribute is used to provide a common set of functions that are performed just before each test method is called. You can also get the Method name from TestContext.CurrentContext.Test.MethodName. There are also other properties on Test like Arguments or FullName depending on what you need.