Test Designer 3: HTML5 and Web Application Compatibility

HTML5

is

Test theDesigner latest3 evolutionsupports modern HTML5-based web applications and many of the standardtechnologies thatcommonly definesused HTML.to Thebuild terminteractive representsweb twoapplications.

different

HTML5 concepts. It is aintroduced new version of the language HTML, with newHTML elements, attributes, APIs, and browser behaviors, andwhile athe largerbroader setmodern ofweb platform includes technologies thatsuch allowsas JavaScript, CSS, browser APIs, and client-side frameworks.

For additional information about HTML and the buildingweb ofplatform, more diverse and powerful Web sites and applications. This set is sometimes called HTML5 & friends and often shortened to just HTML5.see:

There are many pages which detail

• WHATWG HTML 5Standard
• MDN documentationHTML

  Authentication support:

   For Test Designer (An AIQ engine) We support

• Basic authentication

NTLM authentication

Cookies authentication

Digest authentication

ADFS with Kerberos authentication

Active Directory authentication

ADFS with NTLM authentication (ADFS - Extended Protection token check off)

ADFS with Negotiate authentication (ADFS - Extended Protection token check on)

Now,

HTML5 in order to login to AIQ itself, we have

Internal credentials system

LDAP (requires some configuration)

Compatibility

Test Designer supports most ofcommonly theused HTMLHTML5 5features. features,However, butcompatibility becausecan ofdepend theon differenthow waysan aapplication developerimplements its UI components and JavaScript event handling.

Modern web applications can trigger eventsactions inthrough waymultiple differentmechanisms. approachFor thereexample, mightan casesapplication wheremay theuse standard browser events, JavaScript event handlers, CSS pseudo-classes, custom actioncomponents, mightor notframework-specific work.event processing.

E.g.

For clickingAs a button,result, therean are 2 functions, click and click2, most of the time click will work just fine. The reason isaction that clickworks event in TestDesigner triggers every actionwith a standard actionHTML willelement triggermay butbehave theredifferently when the same functionality is alwaysimplemented otherthrough thingsa custom component or JavaScript framework.

Click Actions

Test Designer provides multiple methods for interacting with clickable elements, including click and click2.

In most cases, the developerstandard couldclick doaction likeis usingsufficient. PseduoclassHowever, doingsome applications implement additional JavaScript behavior or custom event handling that may require an alternative click method.

For example, an application may perform additional processing through JavaScript or use CSS pseudo-classes and action.framework-specific event handlers.

For more information abutabout pseudoCSS pseudo-classes, see the MDN CSS pseudo-classes checkhttps://www.w3schools.com/css/css_pseudo_classes.aspdocumentation.

For addingIf a file,standard dueclick toaction does not produce the factexpected therebehavior, istry nothe alternative click method or use an action specifically designed for the application's implementation.

File Upload

HTML5 does not prescribe a single implementation pattern for file-upload interactions across all web applications.

Applications may implement file selection using standard approachHTML toelements, addJavaScript, acustom filecomponents, inor HTMLvframework-specific 5,controls.

To accommodate these implementations, Test Designer provides 4multiple setFiles methods,methods. The appropriate method depends on how the application's file-upload component is implemented.

If a file-upload action does not work as expected, verify the underlying HTML element and the correctapplication's oneJavaScript reallyimplementation, dependsthen onselect the wayappropriate thesetFiles developer has defined the set files. method.

Authentication

Support

As Test Designer injectssupports recordthe following authentication mechanisms:

• Basic Authentication
• NTLM Authentication
• Cookie-Based Authentication
• Digest Authentication
• ADFS with Kerberos Authentication
• Active Directory Authentication
• ADFS with NTLM Authentication when ADFS Extended Protection token checking is disabled
• ADFS with Negotiate Authentication when ADFS Extended Protection token checking is enabled

AIQ Authentication

Authentication to the AIQ application itself can be configured using:

• Internal AIQ credentials
• LDAP authentication, which requires additional configuration

These authentication mechanisms are separate from authentication used by the web applications being automated.

Record and Playback Considerations

Test Designer uses browser instrumentation and injection mechanisms to provide recording and playback tools,capabilities.

Certain application security mechanisms can interfere with these capabilities.

Man-in-the-Middle Detection

Applications or security tools that detect man-in-the-middle (MITM) activity may prevent Test Designer from recording, injecting, or interacting with a “manpage incorrectly.

If an application uses certificate pinning, traffic inspection, or other mechanisms designed to detect intercepted browser traffic, additional configuration may be required.

Browser Certificate Validation

Test Designer may use certificates as part of its browser instrumentation and traffic interception mechanisms.

Depending on the middle”browser mightand application configuration, certificate validation can prevent TestDesigner record and injects or could stop thea page from working.loading correctly or cause the browser to display certificate warnings.

For

example,

browsers

The Browser itself couldmay reject certificates generatesthat bydo TestDesignernot which will rendermatch the certificate expected for a particular domain.

If a page throwingdisplays invalidan certificates.invalid-certificate (E.g.error Googlewhen chromeaccessed rejectsthrough anyTest Designer, verify the browser certificate butconfiguration and the originalapplication's certificatesecurity policies.

JavaScript Framework Support

Test Designer 3 has been tested with commonly used JavaScript frameworks and web technologies, including:

• React
• AngularJS
• Angular
• jQuery
• ExtJS
• Bootstrap

Support for www.google.com)

a framework does

Appvancenot teamnecessarily keepsguarantee addingcompatibility continuous support forwith every HTMLapplication 5built featurewith that framework.

Framework implementations can vary significantly, and majorapplications frameworks.may Currentlyuse custom components, third-party libraries, proprietary event handling, or newer framework versions that behave differently from the versions originally tested.

Compatibility Considerations

Although Test Designer 3.0is supportsdesigned React,to AngularJS,support Angularmodern 4,HTML5 jquery,applications ExtJS,and Bootstrap.commonly Also,used continousweb testingframeworks, compatibility can depend on several factors, including:

• Browser version
• Framework version
• Application architecture
• Custom JavaScript event handling
• Custom web components
• Security and certificate policies
• Third-party browser extensions
• Application-specific DOM behavior
• Framework-specific event handling

New framework releases, major version changes, forks, and highly customized implementations may require additional validation.

When an application does not behave as expected, first determine whether the behavior is donespecific against most ofto the topapplication's websites.implementation or to the underlying framework.

Support and Feature Requests

Appvance continuously evaluates compatibility with modern web technologies and commonly used frameworks.

KeepIf you encounter a web application that does not behave as expected in mindTest evenDesigner, whenprovide the relevant application details, the Test Designer keepsaction being used, and the observed behavior when submitting a support request.

Feature requests and compatibility withissues these frameworks as they are out and HTML5 in general, high recent release or forks might notcan be fullysubmitted supported.

through

the available Appvance team provides several ways for users to connect to customers on support feature requests.channels.