- Have 100 eValid copies running in parallel -- How to avoid, and exploit, intra-browser interactions.
- The size and download data for every page component -- How to measure very-detailed page timings.
- How do you know how those lovely performance charts work? -- All of the charts are Java Applets.
- Running 100 browsers to generate load -- Does channel usage overhead interfere with accurate measurement?
- Pages that have a Modal Popup -- Special tricks for handling modals.
Monday, July 15, 2013
Selected Recent Forum Posts
Wednesday, June 19, 2013
CyberSecurity Resources
A question we are getting recently is:
How can eValid be used to support cybersecurity work?
In other words, given the very specialized needs of searching
for and pinpointing cybersecurity vulnerabilities,
what resources can eValid bring to the table?
For one thing, cybersecurity is a big area, involving a wide range of techniques -- static analysis, dynamic analysis, inspection, and a variety of other options. Because eValid's view is 100% client-side, its technology is only able to provide insight on how things operate from the browser, that is, at the client-side.
But that is in some ways one of the most potentially fruitful areas for which cyber vulnerability analysis can be performed.
As OWASP's section on Testing for AJAX Vulnerabilities points out, the use of AJAX "... the advent of AJAX accounts for an "...Increased Attack Surface..." because AJAX "...throws in additional ways to potentially inject malicious content." In other words, AJAX is an untapped issue in the security world.
eValid can easily handle AJAX applications, and resources inside eValid can then be used to extract the information needed to expose problems due specifically to AJAX application's asynchronous, client-server cooperative nature. So eValid seems to be a good fit for this kind of work, in an area in which it is already strong. The capabilities eValid can supply to a cyberthreat analysis effort are summarized in this CyberSecurity Resource Summary.
For one thing, cybersecurity is a big area, involving a wide range of techniques -- static analysis, dynamic analysis, inspection, and a variety of other options. Because eValid's view is 100% client-side, its technology is only able to provide insight on how things operate from the browser, that is, at the client-side.
But that is in some ways one of the most potentially fruitful areas for which cyber vulnerability analysis can be performed.
As OWASP's section on Testing for AJAX Vulnerabilities points out, the use of AJAX "... the advent of AJAX accounts for an "...Increased Attack Surface..." because AJAX "...throws in additional ways to potentially inject malicious content." In other words, AJAX is an untapped issue in the security world.
eValid can easily handle AJAX applications, and resources inside eValid can then be used to extract the information needed to expose problems due specifically to AJAX application's asynchronous, client-server cooperative nature. So eValid seems to be a good fit for this kind of work, in an area in which it is already strong. The capabilities eValid can supply to a cyberthreat analysis effort are summarized in this CyberSecurity Resource Summary.
Saturday, June 15, 2013
Selected Recent Forum Posts
- Which browser eValid is imitating? -- Details of eValid's neat trick to emulate ANY device!
- Can I use eValid to find out why my pages are loading slowly -- The general method eValid uses to measure detailed timing is revealed.
- A way of capturing the value into a variable in memory -- Tricky manipulations with DOM values have big payoffs.
- Can you do a search from the Address field? -- Guidelines for getting good simple searches done.
- eValid synchronize playback -- The big issue: synchronization of AJAX! Here' the scoop.
Monday, June 10, 2013
How to get a good playback on an AJAX site?
Question:
Do you have any special recommendations for me on how to get a good playback on an AJAX site?
Answer:
Fair question, but also a very broad question.
Web applications that employ AJAX can range from very simple (for example, a simple autocomplete activity), to the very, very complex (for example, the recently introduced http://www.outlook.com email system from Microsoft which they are pitching as better that Gmail).
At a very high level we have found this method of using eValid to test and measure AJAX applications to be the most effective:
(1) Make a recording from life first. "From life" means, using the out-of-the-box settings, make a recording from the starting URL to the point where you are going to be validating a result. The Wait times that eValid puts into your script will, at playback time, provide a crude level of synchronization.
(2) Play the recording back...it ought to work the first time assuming you have not edited the script and are not multiplying the Wait times by the Wait Time Multiplier to make things "go faster."
(3) Now, play back the script increasing the speed -- and increasing the changes for a script de-sync due to AJAX. When the script de-sync's, mark that spot in the playback, go back to that point, and record some kind of synchronization step. Repeat this until you can run your script with the Wait Time Multiplier = 0 -- that is, with NO wait times, but only synchronizations.
To a first level, this will get you a good script. Of course it can become more complex if you want to do structural testing on the page or if you want to replace some parts of your script with fancy DOM manipulations.
_________________
eValid Support
Do you have any special recommendations for me on how to get a good playback on an AJAX site?
Answer:
Fair question, but also a very broad question.
Web applications that employ AJAX can range from very simple (for example, a simple autocomplete activity), to the very, very complex (for example, the recently introduced http://www.outlook.com email system from Microsoft which they are pitching as better that Gmail).
At a very high level we have found this method of using eValid to test and measure AJAX applications to be the most effective:
(1) Make a recording from life first. "From life" means, using the out-of-the-box settings, make a recording from the starting URL to the point where you are going to be validating a result. The Wait times that eValid puts into your script will, at playback time, provide a crude level of synchronization.
(2) Play the recording back...it ought to work the first time assuming you have not edited the script and are not multiplying the Wait times by the Wait Time Multiplier to make things "go faster."
(3) Now, play back the script increasing the speed -- and increasing the changes for a script de-sync due to AJAX. When the script de-sync's, mark that spot in the playback, go back to that point, and record some kind of synchronization step. Repeat this until you can run your script with the Wait Time Multiplier = 0 -- that is, with NO wait times, but only synchronizations.
To a first level, this will get you a good script. Of course it can become more complex if you want to do structural testing on the page or if you want to replace some parts of your script with fancy DOM manipulations.
_________________
eValid Support
Tuesday, May 28, 2013
New eValid Videos Available
We've posted a number of new YouTube videos that relate key information about the eValid solution. The major subjects include:
- RealWorld applications, showing how eValid handles selected testing tasks. An example is the video on Page Timing/Tuning with eValid
- Basic product operation, focusing on how things work in eValid. Examples include Studying DOM Properties with PageMap, and Site Analysis with eValid.
- Complete Webinar recordings, including the important LoadTesting Mobile Web Apps
Wednesday, May 15, 2013
Selected Recent Forum Posts
- Can any functional test be converted to monitoring use? -- Steps to solidify a test for use in monitoring mode.
- The most common kind of error you see in working with AJAX -- Typical AJAX failure modes and how to overcome them.
- Can eValid test a cloud-based application like SalesForce? -- Affirmation of capabilities of testing cloud-based apps.
- eValid tries to write to a SaveRecord file at the same time -- Observations about simultaneity in file processing.
- Explain again how WaitModMM works? -- Watching the clock: modular arithemetic based delays explained.
Sunday, May 5, 2013
Selected Recent Forum Posts
- What are the main components in page rendering? -- Details about how to understand page download and rendering times.
- Does eValid work as a browser without a key? -- How to use eValid even without a license key!
- What is the ACTUAL overhead due to system factors? -- Here are some design facts about eValid's efficiency.
- Can eValid measure two mobile devices at the same time? -- The joys of multiple measurement capability, explained.
- Looking at using XPath to specify tests -- Pros and cons of using Regular Expressions (REs) in test specification.
Subscribe to:
Posts (Atom)