Multi AssertEquals

[Xsi jadu]

Hello everyone,

I am currently is writing an automated test though I am not sure how to handle multiple AssertEquals.

This is my code

if following statements below all of them are true
then print ("test")

RumbaLabel partnr = desktop.<RumbaLabel>find("/WPFWindow[@caption='Terminal - Micro Focus Rumba']//FormsHost[@className='System.Windows.Forms.Integration.WinFormsAdapter']//RumbaScreen//RumbaLabel[@caption='9404099']");
			Assert.assertEquals(false, partnr.isEnptui());
			Assert.assertEquals(false, partnr.isModifiedDataTag());
			Assert.assertEquals(false, partnr.isDetectable());
			Assert.assertEquals(true, partnr.isProtected());
			Assert.assertEquals(false, partnr.isIntense());
			Assert.assertEquals(6, partnr.getEndLine());
			Assert.assertEquals("9404099", partnr.getProperty("caption"));
			Assert.assertEquals("9404099", partnr.getText());
			Assert.assertEquals(false, partnr.isFieldExitRequired());
			Assert.assertEquals(410, partnr.getStartPosition());
			Assert.assertEquals(false, partnr.isAutoEnter());
			Assert.assertEquals(10, partnr.getStartColumn());
			Assert.assertEquals(6, partnr.getStartLine());
			Assert.assertEquals(HostFieldEditConstants.ANY_CHARACTER, partnr.getType());
			Assert.assertEquals(true, partnr.isAutoSkip());
			Assert.assertEquals(8, partnr.getLength());
			Assert.assertEquals(17, partnr.getEndColumn());
			Assert.assertEquals(false, partnr.isHidden());
			Assert.assertEquals(false, partnr.isDup());
			Assert.assertEquals(417, partnr.getEndPosition());

Any ideas how to do this nice and smooth?

Thank you in advance
Regards

Xsi

[Xsi jadu]

Campbell Ritchie wrote:This discussion would fit better in our testing forum. Moving.

I don't agree since its java development I am sure I get more answers in java section.... regardless its for test purpose...

[Stephan van Hulst]

What do you mean by doing it "nice and smooth"?

What's wrong with what you have now?

[Scott Shipp]

One alternative might be to implement an equals() (or deepEquals?) method in RumbaLabel that compares all the fields you care about and just check that partnr is equal to an instance of RumbaLabel with those values. The problem with such an approach, though, is that it would move visibility of what exactly is different out of the test, so I wouldn't recommend it.

[Jeanne Boyarsky]

I recommend using the optional string parameter. That way you know which field is wrong without having to go into the code.

Also, consider using assert softly so you can see all of the assertion failures in one go.