Generally, the invention relates to testing. More specifically, the invention relates to a method for performing intelligent conformance testing of products.
Background
[002] With rapid advancement in field of Information Technology (IT), companies and organizations are rapidly producing IT products and services for meeting current demands of customers. The produced IT products and services should meet current IT standards in order to be successful in market. For this, companies have to focus on quality of IT products and services being developed. Therefore, primary focus of companies during development of IT products is on performing a testing of products while the products are being developed and before they are launched in market. One such testing to ensure delivery of good quality products and services that meets current IT standard includes conformance testing. Conformance testing is defined as testing performed for products to check and ensure that the developed products comply with standards and requirements of a specifications, technical standards, contracts, and regulations.
[003] Currently, in order to perform conformance testing of products during development phase, wireframe model screens are used. Wireframe model screens are nothing but visual representation of the products. In other words, wireframe model screens are interactive prototype of products that may or may not be final product. The wireframe model screens allow develops to easily and quickly test design or layout of the products being developed before visual design and content are added. The wireframe model screens are usually produced by User Experience team to create products that are meaningful and adds relevant experience for users. The wireframe model screen comprises of static data of the products being developed. These

wireframe model screens with static data are compared with developed screen with dynamic data that are produced by User Interface developers. However, manual matching of the wireframe model screens with the developed screens as a part of design conformance testing to identify mismatch between the two screens is challenging and difficult to achieve with higher accuracy. In other words, while performing matching of the two screens manually, a tester may overlook one or more mismatch that may be important to develop the good quality products.
[004] Therefore, there is a need of an efficient and reliable method for performing intelligent conformance testing of products.
SUMMARY OF INVENTION
[005] In one embodiment, a method for performing conformance testing of products is disclosed. The method may include producing a first webpage comprising a set of static data for a product. It should be noted that, the first webpage is produced by exporting a wireframe model screen designed for the product in Hypertext Markup Language (HTML) format. The method may further include developing a second webpage comprising a set of dynamic data for the product. It should be noted that, the second webpage is developed based on the first webpage produced for the product. The method may further include creating a new webpage based on the first webpage and the second webpage. The method may further include generating a model page screenshot based on an execution of the new webpage. The method may further include comparing the model page screenshot with a developed page screenshot using image verification point technique to perform the conformance testing of the product. It should be noted that, the developed page screenshot includes the second webpage.
[006] In another embodiment, a system for performing conformance testing of products is disclosed. The system may include a processor and a memory communicatively coupled to the processor. The memory may store processor-executable instructions, which, on execution, may cause the processor to produce a first webpage comprising a set of static data for a product. It should be noted that, the first webpage is produced by exporting a wireframe model screen designed for the

product in Hypertext Markup Language (HTML) format. The processor-executable instructions, on execution, may further cause the processor to develop a second webpage comprising a set of dynamic data for the product. It should be noted that, the second webpage is developed based on the first webpage produced for the product. The processor-executable instructions, on execution, may further cause the processor to create a new webpage based on the first webpage and the second webpage. The processor-executable instructions, on execution, may further cause the processor to generate a model page screenshot based on an execution of the new webpage. The processor-executable instructions, on execution, may further cause the processor to compare the model page screenshot with a developed page screenshot using image verification point technique to perform the conformance testing of the product. It should be noted that, the developed page screenshot includes the second webpage.
[007] It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
BRIEF DESCRIPTION OF THE DRAWINGS
[008] The present application can be best understood by reference to the following description taken in conjunction with the accompanying drawing figures, in which like parts may be referred to by like numerals.
[009] FIG. 1 illustrates a block diagram of an exemplary system for performing conformance testing of products, in accordance with some embodiments of the present disclosure.
[010] FIG. 2 illustrates a flow diagram of a process for performing conformance testing of products, in accordance with some embodiments of the present disclosure.
[011] FIG. 3 illustrates a flow diagram of an exemplary process for performing conformance testing of a product, in accordance with some embodiments of the present disclosure.
[012] FIG. 4 illustrates an exemplary representation of a technical flow diagram of a process of creating a new webpage, in accordance with some embodiments of the present disclosure.

[013] FIG. 5 illustrates an exemplary representation of a design overview of creating a new webpage, in accordance with some embodiments of the present disclosure.
DETAILED DESCRIPTION OF THE DRAWINGS
[014] The following description is presented to enable a person of ordinary skill in the art to make and use the invention and is provided in the context of particular applications and their requirements. Various modifications to the embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the invention. Moreover, in the following description, numerous details are set forth for the purpose of explanation. However, one of ordinary skill in the art will realize that the invention might be practiced without the use of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order not to obscure the description of the invention with unnecessary detail. Thus, the invention is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed herein.
[015] While the invention is described in terms of particular examples and illustrative figures, those of ordinary skill in the art will recognize that the invention is not limited to the examples or figures described. Those skilled in the art will recognize that the operations of the various embodiments may be implemented using hardware, software, firmware, or combinations thereof, as appropriate. For example, some processes can be carried out using processors or other digital circuitry under the control of software, firmware, or hard-wired logic. (The term "logic" herein refers to fixed hardware, programmable logic and/or an appropriate combination thereof, as would be recognized by one skilled in the art to carry out the recited functions.) Software and firmware can be stored on computer-readable storage media. Some other processes can be implemented using analog circuitry, as is well known to one of ordinary skill in the art. Additionally, memory or other storage, as well as communication components, may be employed in embodiments of the invention.

[016] An exemplary system 100 for performing conformance testing of products is illustrated in FIG. 1. In order to perform conformance testing for a product, the exemplary system 100 may include a testing device 102. The testing device 102 may be configured to produce a first webpage. The first webpage may include a set of static data for the product. Moreover, the testing device 102 may produce the first webpage by exporting a wireframe model screen designed for the product in Hypertext Markup Language (HTML) format. In order to export and design the wireframe model screen for the product, the testing device 102 may use one of a User Experience (UX) design tool. Examples of the UX design tool may include, but is not limited to, Trello, Figma, InVision, Justinmind, MockFlow, Mockingbird, proto.io, Gliffy, Balsamiq, Adobe XD, and Sketch.
[017] Once the first webpage is developed, the testing device 102 may develop a second webpage based on the first webpage produced for the product. The second webpage may include a set of dynamic data for the product. Further, based on the second webpage developed, the testing device 102 may generate a developed page screenshot for the second webpage. The testing device 102 may then create a new webpage based on the first webpage and the second webpage. Once the new webpage is created, the testing device 102 may generate a model page screenshot by executing the new webpage.
[018] Thereafter, the testing device 102 may compare the model page screenshot with the developed page screenshot using image verification point technique to perform the conformance testing of the product. It should be noted that, the image verification point technique may be defined as a technique of verifying images based on pixel to pixel comparison of images. In an embodiment, the images may correspond to the developed page screenshot and the model page screenshot. The comparison of the developed page screenshot with the model page screenshot may be done in order to identify at least one mismatch in the developed page screenshot from the model page screenshot. Further, the testing device 102 may render a result of comparison of the model page screenshot with the developed page screenshot to a user. In an embodiment, the result of comparison may be generated by the testing device 102, based on the at least one mismatch identified. Moreover, this complete process followed by the exemplary system 100 is further explained in detail in conjunction with FIG. 2 to FIG. 5.

[019] Examples of the testing device 102 may include, but are not limited to, a server, a desktop, a laptop, a notebook, a tablet, a smartphone, a mobile phone, an application server, or the like. The testing device 102 may further include a memory 104, a processor 106, and a display 108. The display 108 may further include the user interface 110. The user (e.g., a developer or a tester) may interact with the testing device 102 and vice versa through the display 108.
[020] The display 108 may be used to display results (i.e., the first webpage, the second webpage, the set of dynamic data, the developed page screenshot, the model page screenshot, the report generated based on the comparison, etc.) based on actions performed by the testing device 102, to the user. Moreover, the display 108 may be used to display the at least one mismatch identified in the developed page screenshot based on comparison of the model page screenshot with the developed page screenshot. The at least one mismatch may change based on a new product uploaded for performing conformance testing.
[021] The user interface 110 may be used by the user to provide inputs to the testing device 102. Thus, for example, in some embodiment, the testing device 102 may ingest an input that includes a user selection of the UX tool to export the wireframe model screen in the HTML format. Further, for example, in some embodiments, the testing device 102 may render intermediate results (e.g., the first webpage, the second webpage, the set of dynamic data, the developed page screenshot, the model page screenshot, the at least one mismatch identified) or final results (e.g., the report generated based on the comparison) to the user via the user interface 110.
[022] The memory 104 may store instructions that, when executed by the processor 106, may cause the processor 106 to perform intelligent conformance testing of the product. The processor 106 may perform intelligent conformance testing of the product received from the end-user, in accordance with some embodiments. As will be described in greater detail in conjunction with FIG. 2 to FIG. 5, in order to perform the intelligent conformance testing of the product, the processor 106 in conjunction with the memory 104 may perform various functions including producing the first webpage including the set of static data for the product, developing the second webpage including the set of dynamic data for the product, creating the new webpage, generating the model page screenshot, comparing the model page screenshot with the developed paqe screenshot, updatinq a database 114, etc.

[023] The memory 104 may also store various data (e.g. the first webpage, the second webpage, the set of dynamic data, the developed page screenshot, the model page screenshot, the at least one mismatch identified, the report generated based on the comparison, etc.) that may be captured, processed, and/or required by the testing device 102. The memory 104 may be a non-volatile memory (e.g., flash memory, Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM) memory, etc.) or a volatile memory (e.g., Dynamic Random Access Memory (DRAM), Static Random-Access memory (SRAM), etc.).
[024] Further, the database 114 connected to the testing device 102 may be used to store the first webpage, the second webpage, the set of static data, the set of dynamic data, the at least one mismatch identified. In addition, the database 114 may store the result generated based on comparison of the model page screenshot with the developed page screenshot. Additionally, the database 114 may be periodically updated based on the set of dynamic data and the at least one mismatch identified based on comparison.
[025] Further, the testing device 102 may interact with a server 114 or external devices 120 over a network 118 for sending and receiving various data. The external devices 120 may be used by a plurality of users (i.e., the developer or the tester) to provide their inputs for the product for which the conformance testing may be performed by the testing device 102. The network 118, for example, may be any wired or wireless communication network and the examples may include, but may be not limited to, the Internet, Wireless Local Area Network (WLAN), Wi-Fi, Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), and General Packet Radio Service (GPRS).
[026] In some embodiment, the testing device 102 may fetch information associated with the product from the server 114. In addition, the server 114 may provide access of the information associated with the product to the plurality of users. The server 114 may further include a database 116. The database 116 may store information associated with the product. By way of an example, the database 116 may store the information associated with the product in order to identify suitable UX design tool required for exporting the wireframe model screen to produce the first webpage. The database 116 may be periodically update with a new product or a new UX design

tool. Alternatively, the testing device 102 may receive feedback for the at least one mismatch from the user from one of the external devices 122.
[027] Referring now to FIG. 2 a flow diagram of process 200 for performing conformance testing of products is depicted via flowchart, in accordance with some embodiments of the present disclosure. It should be noted that, for ease of explanation the process 200 for performing the conformance testing is explained for a single product. However, the same process 200 may be used for performing conformance testing of any number of products and services. In order to perform conformance testing of a product, at step 202, a first webpage may be produced for the product. The first webpage produced may include a set of static data associated with the product.
[028] In an embodiment, the first webpage may be produced by exporting a wireframe model screen designed for the product in the HTML format. In order to produce the first webpage, initially, the wireframe model screen may be designed for the product. Once the wireframe model screen is designed, the designed wireframe model screen may be exported in HTML format. In an embodiment, the wireframe model screen may be designed and exported based on one of a UX design tool. Examples of the UX design tool may include, but is not limited to, Trello, Figma, InVision, Justinmind, MockFlow, Mockingbird, proto.io, Gliffy, Balsamiq, Adobe XD, and Sketch.
[029] At step 204, a second webpage may be developed for the product. The second webpage may include a set of dynamic data associated with the product. Moreover, the second webpage may be developed based on the first webpage produced for the product. In order to develop the second webpage, a developed page screenshot may be generated for the second webpage. Once the developed page screenshot is generated, the set of dynamic data may be extracted from the developed page screenshot. Moreover, the set of dynamic data extracted from the developed page screenshot may be rendered to a user. In an embodiment, the user may correspond to a developer or a tester responsible for performing conformance testing for the product.
[030] Once the first webpage and the second webpage are obtained, at step 206, a new webpage may be created based on the first webpage and the second webpage. It should be noted that, the new webpage created may be in the HTML

format. In an embodiment, in order to create the new webpage, the set of static data of the first webpage produced by exporting the wireframe model screen may be replaced with the set of dynamic data extracted from the developed page screenshot. A process of creation of the new webpage has been explained in greater detail in conjunction with FIG. 4 and FIG. 5.
[031] Once the new webpage is created, at step 208, the new web page may be executed to generate a model page screenshot. In other words, in order to generate the model page screenshot, the new webpage may be executed in bowser and a screenshot may be taken thereafter. The screenshot taken after the execution of the new webpage in browser may be referred as the model page screenshot. Further, in order to perform conformance testing of the product, at step 210, the model page screenshot may be compared with the developed page screenshot. In an embodiment, the comparison of the model page screenshot with the developed page screenshot may be done using image verification point technique.
[032] It should be noted that, the image verification point technique may be defined as a technique of verifying images based on pixel to pixel comparison of images. The verification of images may be done to identify difference between two images. In an embodiment, the images may correspond to the developed page screenshot and the model screenshot. Moreover, the comparison of the model page screenshot with the developed page screenshot may be done in order to identify at least one mismatch in the developed page screenshot from the model page screenshot. Further, at step 212, a result of comparison of the model page screenshot with the developed page screenshot may be rendered to the user. Moreover, the result of comparison may be generated based on the at least one mismatch identified in the developed page screenshot from the model page screenshot.
[033] Referring now to FIG. 3, a flow diagram of an exemplary process 300 for performing conformance testing of a product is depicted via flowchart in accordance with some embodiment of the present disclosure. In reference to FIG. 1, the testing device 102 may carry out the exemplary process 300 for performing conformance testing of the product. In order to perform conformance testing of the product, at step 302, a wireframe model screen may be designed for the product. The wireframe model screen may be designed using one of the UX design tool. Examples of the UX design tool may include, but is not limited to, Trello, Figma, InVision, Justinmind, MockFlow,

Mockingbird, proto.io, Gliffy, Balsamiq, Adobe XD, and Sketch. Once the wireframe model screen is designed, at step 304, the designed wireframe model screen may be exported into an HTML page to produce the first webpage. In an embodiment, the designed wireframe model screen may be exported in the HTML page with necessary styles. Moreover, the first webpage developed may include the set of static data associated with the product.
[034] Further, at step 306, the designed wireframe model screen may be utilized to develop the second webpage. The second webpage developed may include the set of dynamic data associated with the product. The second webpage developed may be in the HTML format. In an embodiment, the second webpage may refer to an actual product screen including the set of dynamic data associated with the product. Moreover, in order to develop the second webpage, one of an existing open-source JavaScript library may be used that is focused on development of User Interface (Ul). Examples of the existing open-source JavaScript library may include, but is not limited to, React JS, Inferno JS, Preact, React-Lite, Backbone JS, Aurelia, Ember JS, RiotJS, and jQuery.
[035] Once the second webpage is developed, at step 308, a screenshot of the second webpage may be generated. The screenshot generated for the second webpage may be referred as the developed page screenshot. Upon generating the developed page screenshot, at step 310, the set of dynamic data may be extracted from the developed page screenshot. Further, the extracted set of dynamic data may be rendered to a user on a Ul. In an embodiment, the user may correspond to a developer or a tester responsible for performing conformance testing of the product. In reference to FIG. 1, the UI may correspond to the user-interface 110.
[036] Upon extraction of the set of dynamic data from the developed page screenshot, at step 312, a new webpage may be created. The new webpage may be created by replacing the set of static data of the first webpage obtained at step 304 with the set of dynamic data extracted from the developed page screenshot as obtained at step 310. In an embodiment, the new webpage created may be in the HTML format. A process of creating the new webpage has been explained in greater detail in conjunction to FIG. 4 and FIG. 5. Once the new webpage is created, at step 314, the new webpage may be executed in browser. Upon execution of the new webpage, a screenshot may be taken of result of execution of the new webpage. In

an embodiment, the screenshot taken for the result of execution of the new webpage may be referred as the model page screenshot.
[037] Once the model page screenshot is obtained, at step 316, the model page screenshot may be compared with the developed page screenshot. The comparison of the model page screenshot with the developed page screenshot may be done using image verification point technique to perform the conformance testing of the product. It should be noted that, the image verification point technique may be defined as a technique of verifying images based on pixel to pixel comparison of images. In an embodiment, the images may correspond to the developed page screenshot and the model page screenshot. Further, a result of comparison of the model page screenshot with the developed page screenshot may be rendered to the user.
[038] In an embodiment, the comparison of the model page screenshot with the developed page screenshot may be done in order to identify at least one mismatch in the developed page screenshot from the model page screenshot. In other words, the comparison may enable the user to identify matching items and non-matching items of the developed page screenshot with the model page screenshot. This may provide an advantage to the user by enabling the user to correct the at least one mismatch identified (i.e., the non-matching items), and thereby producing a screen that may conforms to UX design of the product.
[039] Referring now to FIG. 4, an exemplary representation of a technical flow diagram of a process 400 of creating a new webpage is illustrated, in accordance with some embodiments of the present disclosure. In process 400, a set of dynamic data extracted from the developed page screenshot may be stored in a database (also referred as datastore) as depicted via step 402. In reference to FIG. 1, the database may correspond to the database 112. Further, a metadata (i.e., the set of static data for the product) produced by exporting the wireframe model is depicted via step 404.
[040] At step 406, a viewport may be constructed based on the set of dynamic data and the set of static data. In an embodiment, based on the set of dynamic data and the set of static data, the new webpage may be created by processing the first webpage and the second webpage. In order to create the new webpage the set of static data of the first webpage may be replaced with the set of dynamic data extracted from the developed page screenshot. Further, based on the created new webpage,

the viewport may be constructed. In order to construct the viewport, at step 408, a static lifecycle instance may be created for the viewport. In an embodiment, the static lifecycle instance may correspond to the wireframe model screen designed for the product. Once the static lifecycle instance is created, at step 410, a set of parameters may be fetched from the metadata. In an embodiment, the set of parameters may include, but is not limited to assets, Cascading Style Sheets (CSS), and positional parameters. By way of an example, the assets and the CSSs, may enable the user to insert stylesheet while exporting the wireframe model screen into the HTML format. In addition, the positional parameters may enable the user to define position of each screen elements present on the first webpage. Upon fetching the set of parameters, at step 412, the static lifecycle instance created for the viewport may be populated based on the set of parameters fetched from the metadata.
[041] Once the viewport is populated with the set of parameters fetched from the metadata, at step 414, a request may be sent to the database that stores the set of dynamic data to provide dynamic data for each of screen elements. In present FIG. 4, the screen elements may correspond an element (e.g., HTML tags) that add up to a screen. Examples of screen elements may include, but is not limited to, link tags, paragraph tags, anchor tags, list tags, style tags, meta tags, and frame tags.
[042] In one embodiment, upon receiving the request, if the requested dynamic data is available at the database depicted via step 402, then at step 416, the requested data may be provided for further processing. In another embodiment, if the requested data is not available at the database depicted via step 402, then a placeholder text may be sent in a prescribed format for further processing. As will be appreciated, the placeholder text may be defined as a short hint that describes an expected value for an input field.
[043] Upon receiving one of the requested dynamic data or the placeholder text, at step 418, the viewport may be populated based on one of the requested data or the placeholder text received. In order to populate the viewport based on one of the requested data or the placeholder text, a number of iterations may be performed to identify accurate values for the screen elements. Once the viewport is populated, at step 420, the populated viewport may be displayed to the user on browser opened on a screen of a testing device as depicted via step 422. In reference to FIG. 1, the screen may correspond to the display 108 of the testing device 102. It should be noted that,

a user visible area for the viewport may differ based on screen size of the testing devices 102. Examples of testing device may include, but is not limited to, a server, a desktop, a laptop, a notebook, a tablet, a smartphone, a mobile phone, an application server, or the like.
[044] Various embodiments provide method and system for performing conformance testing of products. In particular, the disclosed method and system, described in various embodiments discussed above, may produce a first webpage comprising a set of static data for a product. The first webpage is produced by exporting a wireframe model screen designed for the product in Hypertext Markup Language (HTML) format. The disclosed method and system may develop a second webpage comprising a set of dynamic data for the product. The second webpage is developed based on the first webpage produced for the product. Further, the disclosed method and system may create a new webpage based on the first webpage and the second webpage. Moreover, the disclosed method and system may generate a model page screenshot based on an execution of the new webpage. In addition, the disclosed method and system may compare the model page screenshot with a developed page screenshot using image verification point technique to perform the conformance testing of the product. The developed page screenshot includes the second webpage.
[045] The disclosed method and system provide some advantages like, the disclosed method and system may enable easy comparison of the developed page screenshot and the model page screenshot of the product. The disclosed method and the system may match the model page screenshot with the developed page screenshot with higher accuracy. This may enable easy and accurate identification of at least one mismatch in the developed page screenshot from the model page screenshot. Further, the disclosed method and system may work in conjunction with any Ul design tool (e.g., Figma tool) for performing conformance testing of products.
[046] It will be appreciated that, for clarity purposes, the above description has described embodiments of the invention with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functionality between different functional units, processors or domains may be used without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as

references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
[047] Although the present invention has been described in connection with some embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention.
[048] Furthermore, although individually listed, a plurality of means, elements or process steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather the feature may be equally applicable to other claim categories, as appropriate.

CLAIMS
WHAT IS CLAIMED IS:
1. A method (200) for performing conformance testing of products, the method (200)
comprising:
producing (202), by a testing device (102), a first webpage comprising a set of static data for a product, wherein the first webpage is produced by exporting a wireframe model screen designed for the product in Hypertext Markup Language (HTML) format;
developing (204), by the testing device (102), a second webpage comprising a set of dynamic data for the product, wherein the second webpage is developed based on the first webpage produced for the product;
creating (206), by the testing device (102), a new webpage based on the first webpage and the second webpage;
generating (208), by the testing device (102), a model page screenshot based on an execution of the new webpage; and
comparing (210), by the testing device (102), the model page screenshot with a developed page screenshot using image verification point technique to perform the conformance testing of the product, wherein the developed page screenshot includes the second webpage.
2. The method (200) as claimed in claim 1, wherein producing (202) the first webpage
comprises:
designing, by the testing device (102), the wireframe model screen for the product; and
exporting, by the testing device (102), the wireframe model screen designed for the product in HTML format, wherein the designed wireframe model screen is exported

to produce the first webpage, and wherein the wireframe model screen is designed and exported based on a User Experience (UX) design tool.
3. The method (200) as claimed in claim 1, wherein developing (204) the second
webpage comprises:
generating, by the testing device (102), the developed page screenshot for the second webpage; and
extracting, by the testing device (102), the set of dynamic data from the developed page screenshot, wherein the set of dynamic data is rendered to a user upon extraction.
4. The method (200) as claimed in claim 1, wherein creating (206) the new webpage comprises replacing, by the testing device (102), the set of static data of the first webpage produced by exporting the wireframe model screen with the set of dynamic data extracted from the developed page screenshot.
5. The method (200) as claimed in claim 1, wherein comparing (210) the model page screenshot with the developed page screenshot comprises:
matching, by the testing device (102), the model page screenshot with the developed page screenshot to identify at least one mismatch in the developed page screenshot from the model page screenshot; and
rendering (212), by the testing device (102), a result of comparison of the model page screenshot with the developed page screenshot to the user, wherein the result of comparison is generated based on the at least one mismatch identified.
6. A system (100) for performing conformance testing of products, the system (100)
comprising:

a processor (106); and
a memory (104) communicatively coupled to the processor (106), wherein the memory (104) stores processor executable instructions, which, on execution, causes the processor (106) to:
produce (202) a first webpage comprising a set of static data for a product, wherein the first webpage is produced by exporting a wireframe model screen designed for the product in Hypertext Markup Language (HTML) format;
develop (204) a second webpage comprising a set of dynamic data for the product, wherein the second webpage is developed based on the first webpage produced for the product;
create (206) a new webpage based on the first webpage and the second webpage;
generate (208) a model page screenshot based on an execution of the new webpage; and
compare (210) the model page screenshot with a developed page screenshot using image verification point technique to perform the conformance testing of the product, wherein the developed page screenshot includes the second webpage.
7. The system (100) as claimed in claim 6, wherein, to produce (202) the first webpage, the processor executable instructions cause the processor (106) to:
design the wireframe model screen for the product; and
export the wireframe model screen designed for the product in HTML format, wherein the designed wireframe model screen is exported to produce the first webpage, and wherein the wireframe model screen is designed and exported based on a User Experience (UX) design tool.

8. The system (100) as claimed in claim 6, wherein, to develop (204) the second
webpage, the processor executable instructions cause the processor (106) to:
generate the developed page screenshot for the second webpage; and
extract the set of dynamic data from the developed page screenshot, wherein the set of dynamic data is rendered to a user upon extraction.
9. The system (100) as claimed in claim 6, wherein, to create (206) the new webpage,
the processor executable instructions cause the processor (106) to replace the set of
static data of the first webpage produced by exporting the wireframe model screen
with the set of dynamic data extracted from the developed page screenshot.
10. The system (100) as claimed in claim 6, wherein, to compare (210) the model
page screenshot with the developed page screenshot, the processor executable
instructions cause the processor (106) to:
match the model page screenshot with the developed page screenshot to identify at least one mismatch in the developed page screenshot from the model page screenshot; and
render (212) a result of comparison of the model page screenshot with the developed page screenshot to the user, wherein the result of comparison is generated based on the at least one mismatch identified.