Wednesday, September 24, 2014

Selected Recent Forum Posts

Here are some selected posts from our eValid forum:

eValid versus WebDriver -- A short comment, probably of interest to everyone, about how eValid compares with the WebDriver open-source web driving solution.

Can I use eValid's DOM ability to change a value. -- It may surprise you but yes, eValid can actually read and write from/to the current page's DOM. This post points out how you do this with simple eValid commands.

What do you mean by: "recording protocol" -- Some types of websites, AJAX applications for example, can have tests recorded "out of the box" so that they incorporate self-synchronizing capability, using a special way of making the recording.

Special Methods -- Very often we are asked, how did we build eValid? This post gives you a rough outline of how eValid is built and maintained.

Friday, September 12, 2014

eValid -- SmartPhone/Tablet Leverage Analysis

The eValid Patents are key resources of importance to companies involved in the mobile device space (tablets and smartphone) because they apply to the way in which web applications for these platforms are developed and delivered.

The Mobile Device Space

Among the ~5 Billion cellphones and tablets in the world, ~1 Billion are smartphones or web enabled tablets. The device counts are growing rapidly.

Apps (including web apps) that run on these devices are equally numerous. The Apple app store has ~700K iPhone and iPad apps (~400K iPhone and ~300K iPad). Google has recently (October 2012) tied Apple with over ~700K Android apps.

Major suppliers of SDKs for these tablet/smartphone devices include: Apple's iOS 10.n; Google's Android SDK; Microsoft's VS2010/2012 on W8/RT, and Surface SDK 8.0; Blackberry's BB10 SDK; Mozilla's Firefox OS's SDK; Samsung's variant of Android SDK; Ubuntu's variant of Android SDK; and Tizen's Magnolia SDK.

Web App Qualification Support
Most suppliers control/gate the entry of [web] apps into their [web] app "store" via some kind of QA certification, supported for their devices in their own SDKs. All suppliers (except Microsoft) rely on the WebKit Rendering Engine, originally developed for the Apple Safari browser and now open-sourced; Microsoft relies on its proprietary Trident Rendering Engine, used in the IE browser family.

Wherever the WebKit base is used, the above SDK's use test engines that rely on the Selenium browser-based Google WebDriver API, already a defacto standard and now a W3C Working Draft on the way to becoming the standard. Microsoft uses VS2010/2012's CUIT browser driver.

The existence in all of the suppliers' systems of support for HTML5 assures that even native apps for mobile platforms will easily migrate to full featured web apps.

Web apps need careful and thorough testing before being accepted for inclusion in one of the app stores. Such web application testing involves utilizing features and capabilities that are the subject of the eValid patent portfolio. Such capabilities include the ability to synchronize AJAX testing via DOM interrogation, the ability to test internal page content with DOM extraction, and the ability to provide detailed timing/performance data based on collecting fine-scale DOM-centric data about web page behavior.

The eValid patents thus represent an extremely valuable resource to any company involved in this technology area.

Wednesday, September 10, 2014

Selected Recent Forum Posts

Here are some selected posts from our eValid forum:

Using eValid to test a website in Hindi -- Just a reminder: eValid does have DBCS capability but only in the international Edition.

Trouble with a form webpage -- Here is a simple explanation of how to adjust an eValid script to handle a web-form "click on this" action by adding in the NO_NAV tag on the eValid commands.

Structural Testing Question -- An overview and key documentation pages about how to use eValid in Structural Testing mode in which actions are taken on the Document Object Model (DOM) behind the web page that you see.

Trouble with a button using IndexClick command -- More detail on handling intended and unintended browser naviations, picking up where the above post left off.