bizunit Work Item Rss Feed

Created Issue: The BizUnit.TestSteps.File.ExistsStep does not honor the TimeOut value [19253]

JakobEskar — Fri, 25 Jan 2013 12:25:29 GMT

The Execute method will throw an exception even if the timeout has not been reached

Created Issue: Validate a message from MSMQ test step [18881]

abhijitdutta — Thu, 08 Nov 2012 06:39:14 GMT

i have a scenario where i need to validate a message from MSMQ
the message is an xml one and i need to validate against a schema and aswell against a xpath..
the xpath one is always returning all the values as a string

Created Issue: Validation Steps Missing [18880]

abhijitdutta — Thu, 08 Nov 2012 06:37:07 GMT

There are some validation steps which are deprecated in 4.0 but very essential like Regex,binary validator

Created Issue: No proper WCF test step [18879]

abhijitdutta — Thu, 08 Nov 2012 06:35:59 GMT

there is no WCF test step..only soap/http test tseps are provided which are not sufficient in the WCF era.

Created Issue: Problem with MAP testing with Bizunit [18859]

SoumenDatta — Mon, 05 Nov 2012 14:22:36 GMT

While I am testing the Biz-talk Map Xpath result is concatenating all the value of each element under the Schema.

Created Issue: NuGet package for BizUnit [18832]

schalkvanwyk — Wed, 31 Oct 2012 14:31:59 GMT

The MSI is great, but NuGet would make some people's life a little easier.

Commented Issue: FilePathsToDelete Error [16262]

jcooper1982 — Wed, 06 Jun 2012 21:20:42 GMT

Below my code:

var delete = new DeleteStep();
delete.FilePathsToDelete.Add("C:\\Test\\Out\\*.xml");
delete.Execute(new Context());

I am getting "Object reference not set to an instance of an object." error in line 2. What am I doing wrong?

Thank you.
Comments: ** Comment from web user: jcooper1982 **

Also see the fix suggested in issue #18194 - changing the default constructor to ensure that the collection is instantiated when the test step is instantiated.

Created Issue: DeleteStep fails when read in from a XAML TestCase [18194]

jcooper1982 — Wed, 06 Jun 2012 21:18:42 GMT

When executing a TestCase that is read in from a XAML file, the DeleteStep will always fail as the FilePathToDelete collection is not properly instantiated.

Creating a default constructor like the below allows the DeleteStep to be properly instantiated by the XAML deserializer.

/// <summary>
/// Default constructor which ensures that FilePathsToDelete is instantiated and thus the DeleteStep can deserialize properly.
/// </summary>
public DeleteStep()
{
FilePathsToDelete = new Collection<string>();
}

Note that this might be a problem with other test steps that make use of collections.

Commented Issue: FilePathsToDelete Error [16262]

KurtEwald — Fri, 11 May 2012 09:29:37 GMT

Hello,

I have experienced the same problem. I am about to create a .exe command
line tool, which is able to execute Xaml BizUnit 4.0 tests.

1) I have already considered the comments given above, but I still experience this
problem. I don' have any glue. Any help will be highly appreciated.

2) Is there already a ready made command line tool provided by BizUnit, which is able to execute a Xaml testcase from the cmd command line?

Ad 1) I have attached the Xaml sample testcase, which I am trying to execute.

Thanks in advance!

Best regards

Kurt

Commented Issue: ExistsStep.SeachPattern Error:Directory does not contain the correct number of files!Found: 0 files matching the pattern [17351]

HaraldWolkenfelt — Wed, 09 May 2012 11:36:09 GMT

Hi,

I am writing unit test for BizTalk 2010 application using BizUnit4.0 framework. The unit test is written for testing to check file is received at the output fileshare. I am getting the below error "System.ApplicationException: Directory does not contain the correct number of files!
Found: 0 files matching the pattern ".
But the same test passes while i am debugging via BizUnit source code. I have tried specifing the timeout via .Timeout and increased it to 3 minutes. But still no luck.

Any help is greatly apprecieated.

Thanks,
Basawa
Comments: ** Comment from web user: HaraldWolkenfelt **

I reworked the ExistsStep like this:

public override void Execute(Context context)
{
var now = DateTime.Now;
string[] filelist = null;
bool foundCorrectNo = false;

do
{
Thread.Sleep(500);

// Get the list of files in the directory
filelist = Directory.GetFiles(DirectoryPath, SearchPattern);

if (filelist.Length == ExpectedNoOfFiles)
{
foundCorrectNo = true;
break;
}

} while (now.AddMilliseconds(Timeout) > DateTime.Now);

context.LogInfo("FilesExistStep found: \"{0}\" files", filelist.Length);

if (!foundCorrectNo)
{
// Expecting more than one file
throw new ApplicationException(
String.Format(
"Directory does not contain the correct number of files!\n Found: {0} files matching the pattern {1}.",
filelist.Length,
SearchPattern));
}
}

Commented Issue: ExistsStep.SeachPattern Error:Directory does not contain the correct number of files!Found: 0 files matching the pattern [17351]

HaraldWolkenfelt — Wed, 09 May 2012 11:17:20 GMT

I do think it is an issue.
In the (tight) do{}while loop, the exception is immediately thrown without consideration of the timeout.
When debugging, you get a timeout due to your slow-stepping.
The implementation of the now obsolete BizUnit.CoreSteps.TestSteps.FilesExistStep does work.

Harald

Commented Issue: XmlValidationStep not failing when wrong schema is specified [17602]

desanghi — Thu, 03 May 2012 08:37:20 GMT

When a schema is specified which is complete mismatch for the xml document, the XmlValidationStep succeeds.

XmlValidationStep should validate that a schema URI has been specified for all namespace URIs used in the XML instance.

For an example of how this can be solved, see the ValidateSchemaNameSpaces method in the attached file.
Comments: ** Comment from web user: desanghi **

I have also encountered the same issue. The issue were:
1) This step does not validate the namespace of the xml with the XSD.
2)IF i give a totally different xml, even then it doesn't fail.

I have modified the code for XMLValidationStep.cs and also tested it.
I request you to test it and it is simpler than the code written by you.

The changes in ValidateXmlInstance Function is :
//Added new Logic for Validation
settings.ValidationFlags = XmlSchemaValidationFlags.ReportValidationWarnings;
// set validation handler
settings.ValidationEventHandler += new System.Xml.Schema.ValidationEventHandler(ValidationEventHandler);
//End

The changes in ValidationEventHandler Function is :
void ValidationEventHandler(object sender, ValidationEventArgs e)
{
switch (e.Severity)
{
case XmlSeverityType.Error:
_context.LogError(e.Message);
_validationException = e.Exception;
break;
case XmlSeverityType.Warning:
_context.LogWarning(e.Message);
_validationException = e.Exception;
break;
}
//Added Code for Validation
throw new XmlException("XML data is not valid."+e.Message);
//Code Ended

}

Created Issue: XmlValidationStep not failing when wrong schema is specified [17602]

shundeide — Wed, 14 Mar 2012 13:11:40 GMT

When a schema is specified which is complete mismatch for the xml document, the XmlValidationStep succeeds.

According to the MSDN specification for XmlReaderSettings a warning event is only fired when the
XmlSchemaValidationFlags.ReportValidationWarnings has been set:
http://msdn.microsoft.com/en-us/library/system.xml.xmlreadersettings.validationflags.aspx

The fix is to set this attribute on the XmlReaderSettings (in method ValidateXmlInstance in class XmlValidationStep):
settings.ValidationFlags |= XmlSchemaValidationFlags.ReportValidationWarnings;

Created Issue: FactBasedRuleEngineStep not passing facts to PolicyTester [17506]

turkeys_united — Wed, 29 Feb 2012 03:14:48 GMT

I'm using BizUnit 4.0 (4.0.154.0) to create unit tests for my BRE policies. Unfortunately when the test is executed, I receive an exception "BizUnit.TestStepExecutionException: BizUnit encountered an error executing a test step ---> System.NullReferenceException: Object reference not set to an instance of an object."

I tracked this down to the FactBasedRuleEngineStep, in particular it appears to be because the Execute method uses a switch statement based on currentFact.GetType().ToString() to determine how to create and pass BRE facts to the PolicyTester, but the specific cases look like they expect only the type's Name (eg "ObjectFact"), not its Fullname (eg "BizUnit.TestSteps.BizTalk.Bre.ObjectFact") which is what ToString() returns... hence no cases in the switch statement match, and no facts are passed into the PolicyTester.

Commented Issue: ExistsStep.SeachPattern Error:Directory does not contain the correct number of files!Found: 0 files matching the pattern [17351]

basawa_raj — Fri, 03 Feb 2012 18:55:32 GMT

Sorry this not the issue , i have mistakely created in the Issue Trakcer

Created Issue: ExistsStep.SeachPattern Error:Directory does not contain the correct number of files!Found: 0 files matching the pattern [17351]

basawa_raj — Fri, 03 Feb 2012 18:49:25 GMT

Commented Issue: [Feature Request] Multiple Validation Steps [15903]

charliemott — Fri, 06 Jan 2012 16:28:05 GMT

I would be keen to have the ability to run multiple validation sub-steps for a test step. For example, I have an MSMQ read step. Against this message data I would like to run: the Xml Schema validation test step to ensure the whole message is valid against schema; and a also run a custom validation step that test certain parts of the message against business rules.
Comments: ** Comment from web user: charliemott **

Top Tip. In a BizUnit version 4 Sub Steps, reset the poistion of the steam in the Execute method after use. The steam will then be available to subsequent sub steps.

public override Stream Execute(Stream data, Context context)
{
< validation logic here>
data.Position = 0; // reset position so stream is available to subsequent sub-steps.
return data;
}

Created Issue: FactBasedRuleEngineStep not executing validation steps [16985]

ChrisRomp — Wed, 30 Nov 2011 20:32:24 GMT

Version 3.1.1001.0.

I've noticed that no XML validation was being done on my BRE tests in BizUnit. Upon further investigation, I noticed this in FactBasedRuleEngineStep.cs from the source (starts at line 240):

// Validate if configured...
// HACK: We need to prevent ExecuteValidator for /each/ TypedXmlDocument
if (txd.DocumentType == "UBS.CLAS.PoC.Schemas.INSERTS")
{
context.ExecuteValidator(data, validationConfig);
}

Was this intentional? How can I get validation to work on rules tests?

Commented Issue: FilePathsToDelete Error [16262]

TychoLien — Fri, 19 Aug 2011 10:14:22 GMT

Change your code to:

var delete = new DeleteStep();
var filePathsToDelete = new Collection<string> {"C:\\Test\\Out\\*.xml"};

delete.FilePathsToDelete = filePathsToDelete;
delete.Execute(new Context());

That'll work

Created Issue: FilePathsToDelete Error [16262]

mkonda — Mon, 18 Jul 2011 22:10:43 GMT