Wednesday, June 25, 2014

Selected Recent Forum Posts

Here are some selected posts from our eValid forum:

Why is scaling so important? -- Some practical answers that point to one of evalid's best selling points.

 eValid rendering Chrome question All about rendering, and does it make a difference or not in doing regression testing of web applications.

 Using eValid to monitor a page being hacked -- The key requirement for eValid to detect a page having been hacked is to have some kind of checksum of the page.

  LoadRunner vs. eValid question -- Why eValid's archtecture precludes the need for a "correlation capability."

Monday, June 16, 2014

eValid Component Licensing Options

With the recent completion of the primary set of eValid Patents, we have begun to set up offerings of key eValid technologies as part of the eValid Business Development activity.

Our technology covers virtually all functions needed for client-side analysis of web browser enabled applications including performance, timing, behavior, quality, security, and reliability. The technology is effectively a "one stop shop" for client-view web application testing and analysis.

If you are interested in eValid components for your own application you ought to look at the available Component Descriptions.

Please contact us directly for additional details.

Wednesday, June 11, 2014

JavaScript Error in JQuery Examples

A little-known feature of eVald -- but which many eValid users know about and use regularly -- is it's ability to identify JavaScript errors. During test playback, when the browser is active and processing intake of JavaScript components, any JavaScript errors that are detected by the JavaScript thread are reported in the playback EventLog.

Usually such errors are not important, and are caused mostly by typos or other small flaws that do not interfere with operation of the page that includes them. However, we have found a case in which a very severe problem is traced to a JavaScript fault. How the JQueryMobile site's demos page locks up (and how the eValid playback detects the faulty JavaScript passage) is described here: JQueryMobile JavaScript Error Explanation

The "JQuery Mobile 1.3.2 Demos" version, which causes the problem, is labeled as a Legacy Version. The more recent JQuery Mobile 1.4.2 Demos" version works fine! Obviously someone fixed the problem in the excellent JQuery Mobile product!

Tuesday, June 10, 2014

Selected Recent Forum Posts

Here are some selected posts from our eValid forum:

Why is doing my web security test from within a browser -- Many have asked "why is the from-the-browser view so important? Here is part of the answer.

Require any special permission to analyze a website -- Just a confirmation: no access credentials needed to browse or test a public website.

Site Analysis slows after 1000 pages. Problems??? -- Indeed, there are, after all, only computers, and therefore in com instances you do get a performance hit.

Question on rendering difference checkers -- More about the issue of how pages render in different browser's renderers.

Wednesday, June 4, 2014

Selected Recent Forum Posts

Here are some selected posts from our eValid forum:

Easier time when dealing with AJAX -- The easy way to make sure an AJAX application yields a reliable (self-synchronizing) test playback.

Question that have to do with reporting engines -- Details about the SQL interface that is available through the eValid Programmatic Interface (EPI).

Security Testing -- A simple illustration of how to find non-trivial vulnerabilities.

The easiest way to get 1000 users launched on one machine -- It isn't magic at all -- just the application of basic software engineering skills.