Comparing 2 images for equality - Revision history

Wikicatglobe at 10:38, 17 October 2013

2013-10-17T10:38:21Z

← Older revision		Revision as of 10:38, 17 October 2013
Line 1:		Line 1:
	<accesscontrol>~~Administrators,,Cem,,Maysunshine~~</accesscontrol>		<accesscontrol>Main:MyGroup</accesscontrol>
	[[Category:Miscellaneous]]		[[Category:Miscellaneous]]
	== Introduction ==		== Introduction ==

Cg_pham at 09:46, 24 October 2011

2011-10-24T09:46:18Z

← Older revision		Revision as of 09:46, 24 October 2011
Line 1:		Line 1:
	<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>		<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>
	[[Category:~~Guidelines~~]]		[[Category:Miscellaneous]]
	== Introduction ==		== Introduction ==
	At the time of writing this page, we are testing the affection of changing stylesheet manually. This is not a good way of testing, because there are more than 2000 settings in stylesheet, and testers simply can't re-test over and over again. So, we come to a decision of making some automatic testing tool that can assert the correctness of diagrams.		At the time of writing this page, we are testing the affection of changing stylesheet manually. This is not a good way of testing, because there are more than 2000 settings in stylesheet, and testers simply can't re-test over and over again. So, we come to a decision of making some automatic testing tool that can assert the correctness of diagrams.

Cg_pham at 07:17, 5 October 2011

2011-10-05T07:17:27Z

← Older revision		Revision as of 07:17, 5 October 2011
Line 1:		Line 1:
			<accesscontrol>Administrators,,Cem,,Maysunshine</accesscontrol>
			[[Category:Guidelines]]
	== Introduction ==		== Introduction ==
	At the time of writing this page, we are testing the affection of changing stylesheet manually. This is not a good way of testing, because there are more than 2000 settings in stylesheet, and testers simply can't re-test over and over again. So, we come to a decision of making some automatic testing tool that can assert the correctness of diagrams.		At the time of writing this page, we are testing the affection of changing stylesheet manually. This is not a good way of testing, because there are more than 2000 settings in stylesheet, and testers simply can't re-test over and over again. So, we come to a decision of making some automatic testing tool that can assert the correctness of diagrams.

Catglobe: add note

2009-05-25T06:41:37Z

add note

← Older revision		Revision as of 06:41, 25 May 2009
Line 5:		Line 5:

	Then it comes to SVG image format as a good candidate. SVG stands for Scalable Vector Graphic which stores image in XML format. Thus, comparing 2 images becoming comparing 2 XML files. SVG image can be viewed using IE with a plugin from Adobe call [http://www.google.com.vn/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fwww.adobe.com%2Fsvg%2Fviewer%2Finstall%2F&ei=Yg3oSZ-2IsGIkAX4hOWiBw&usg=AFQjCNHNUB67KnsQkkQ1E3ig5-nKYdQOXw&sig2=B5l8uI_MZIOzqKY0OK13lw SVGViewer]		Then it comes to SVG image format as a good candidate. SVG stands for Scalable Vector Graphic which stores image in XML format. Thus, comparing 2 images becoming comparing 2 XML files. SVG image can be viewed using IE with a plugin from Adobe call [http://www.google.com.vn/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fwww.adobe.com%2Fsvg%2Fviewer%2Finstall%2F&ei=Yg3oSZ-2IsGIkAX4hOWiBw&usg=AFQjCNHNUB67KnsQkkQ1E3ig5-nKYdQOXw&sig2=B5l8uI_MZIOzqKY0OK13lw SVGViewer]

			<font color='red'>'''Note''': there is a limitation with SVG support in Nevron, at the time of writing (05.2009) CatGlobe system is still using a very old version of Neveron (Q4-2007) which does not support for SVG very well, almost diagrams do not work well in SVG mode. However, the newest version (Q1-2009) supports SVG rather well. SVG format in itself contains a limitation that it cannot display 3D images. As conclusion, only develop testing with this article with Q1-2009 or newer version of Nevron, and only test on 2D chart.</font>

	== Nevron chart and SVG ==		== Nevron chart and SVG ==

Catglobe: /* NUnit XML Assertion */

2009-05-20T09:21:01Z

NUnit XML Assertion

← Older revision		Revision as of 09:21, 20 May 2009
Line 87:		Line 87:
	</source>		</source>

	Of course, references to assemblies (CatGlobe.NUnit.Addins.dll, XmlDiffPatch.dll, XmlDiffPath.View.dll) must be added to the unit test project. The assertion result is displayed on screen like this:		'''Of course, references to assemblies (CatGlobe.NUnit.Addins.dll, XmlDiffPatch.dll, XmlDiffPath.View.dll) must be added to the unit test project.''' The assertion result is displayed on screen like this:

	[[Image:XMLAssertResult.png]]		[[Image:XMLAssertResult.png]]

Catglobe: Create the first version

2009-04-17T05:05:53Z

Create the first version

New page

== Introduction ==
At the time of writing this page, we are testing the affection of changing stylesheet manually. This is not a good way of testing, because there are more than 2000 settings in stylesheet, and testers simply can't re-test over and over again. So, we come to a decision of making some automatic testing tool that can assert the correctness of diagrams.

However, there are charts that are generated as images in report system. Comparing 2 images pixel by pixel is not a bad idea in terms of at least having something that make sure our system is still working. But the image comparing have limitation in pointing out exactly the differences (in label, in color etc...)

Then it comes to SVG image format as a good candidate. SVG stands for Scalable Vector Graphic which stores image in XML format. Thus, comparing 2 images becoming comparing 2 XML files. SVG image can be viewed using IE with a plugin from Adobe call [http://www.google.com.vn/url?sa=t&source=web&ct=res&cd=1&url=http%3A%2F%2Fwww.adobe.com%2Fsvg%2Fviewer%2Finstall%2F&ei=Yg3oSZ-2IsGIkAX4hOWiBw&usg=AFQjCNHNUB67KnsQkkQ1E3ig5-nKYdQOXw&sig2=B5l8uI_MZIOzqKY0OK13lw SVGViewer]

== Nevron chart and SVG ==
Generating chart image to SVG with Nevron chart control (the main control that we are using for generating chart image) is as easy as below code;

<source lang="csharp">
NSvgImageFormat svgImageFormat = new NSvgImageFormat();
svgImageFormat.Compress = false;
nChartControl1.CreateImage(svgImageFormat).SaveToFile(@"D:\svn" + DateTime.Now.ToString("ddMMyyyy_hhmmss")+".svg", new NSvgImageFormat());
</source>

== XML Comparision ==
Microsoft provides free tools called [http://download.microsoft.com/download/1/f/1/1f146f9b-2a71-4904-8b91-e2f62d7b64b3/XmlDiffPatch.exe XMLDiffPatch] for comparing/synchronizing 2 XMLs.

In this download, you can also find an XmlDiffPatch.View which process the diff result and generate HTML report. Which looks something like this
[[Image:XMLDiffPath.View.png]]

== NUnit XML Assertion ==
The implementation of the XML assertion can be found under ''CatGlobe\Components\CatGlobe.NUnit.Addins''.

There are a couple of methods for asserting the equality of XML (stream, fragment, file) as below:

<source lang="csharp">
public class XmlAssert
{
/// <summary>
/// Assert the 2 XML stream for equality.
/// </summary>
/// <param name="expectedXmlStream">Expected XML Stream</param>
/// <param name="actualXmlStream">Actual XML Stream</param>
public static void AreEqual(Stream expectedXmlStream, Stream actualXmlStream);

/// <summary>
/// Assert the 2 XML stream for equality.
/// </summary>
/// <param name="expectedXmlStream">Expected XML Stream</param>
/// <param name="actualXmlStream">Actual XML Stream</param>
/// <param name="message">Customer display message when the 2 streams are not equal</param>
/// <param name="args">Arguments use for formatting the <paramref name="message"/></param>
public static void AreEqual(Stream expectedXmlStream, Stream actualXmlStream, string message, params object[] args);

/// <summary>
/// Assert the 2 XML fragments for equality.
/// </summary>
/// <param name="expectedXmlStream">Expected XML fragment</param>
/// <param name="actualXmlStream">Actual XML fragment</param>
public static void AreEqual(string expectedXml, string actualXml);

/// <summary>
/// Assert the 2 XML fragments for equality.
/// </summary>
/// <param name="expectedXmlStream">Expected XML fragment</param>
/// <param name="actualXmlStream">Actual XML fragment</param>
/// <param name="message">Customer display message when the 2 fragments are not equal</param>
/// <param name="args">Arguments use for formatting the <paramref name="message"/></param>
public static void AreEqual(string expectedXml, string actualXml, string message, params object[] args);

/// <summary>
/// Assert the 2 XML file for equality.
/// </summary>
/// <param name="expectedXml">Expected XML file</param>
/// <param name="actualXml">Actual XML file</param>
public static void AreEqualXmlFile(string expectedXml, string actualXml);

/// <summary>
/// Assert the 2 XML file for equality.
/// </summary>
/// <param name="expectedXml">Expected XML file</param>
/// <param name="actualXml">Actual XML file</param>
/// <param name="message">Customer display message when the 2 files are not equal</param>
/// <param name="args">Arguments use for formatting the <paramref name="message"/></param>
public static void AreEqualXmlFile(string expectedXml, string actualXml, string message, params object[] args);
}

</source>

The asserts are used as any other normal assert methods. See code below:

<source lang="csharp">
XmlAssert.AreEqual("<test />", "<test>fasdfd</test>");
XmlAssert.AreEqualXmlFile(@"D:\svn09042009_045701.svg", @"D:\svn09042009_045701_new.svg");
</source>

Of course, references to assemblies (CatGlobe.NUnit.Addins.dll, XmlDiffPatch.dll, XmlDiffPath.View.dll) must be added to the unit test project. The assertion result is displayed on screen like this:
[[Image:XMLAssertResult.png]]

The HTML report is generate using XmlDiffPatch.View.dll would looking something like the first image in this article. There is a setting in .config file for shutting down the report generation (in case, we just want to know if there is an error and don't care about what exactly are the errors). This can save some speed for running the unit test.

<source lang="xml">

<add key="GenerateXMLComparisionReport" value="false" />
</source>

== Possible optimization ==
For HTML report, there are possible optimization as
# Add jump to next different.
# Display line number.
# Skip same parts with some text "Skip xxxx lines that are the same." to reduce HTML file size and speed up comparision.