The following operators can be used to better focus your queries.
( ) , AND, OR, NOT, W/#
? single char wildcard, not at start
* multi char wildcard, not at start
(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*
This guide provides a more detailed description of the syntax that is supported along with examples.
This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.
Concept Search - What can I type?
For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.
Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.
This will document a method, using industry standard test tools
based on 'capture' technology, to playback features of your application
that are not consistent between test runs.
English (United States)
This text was extracted from a PDF file.
This is the abbreviated version, containing approximately
69% of the total text.
Page 1 of 1
Method to Capture and Playback Binary Unique Data in Test Tools
With current test tools in the marketplace (Loadrunner, Rational), there are methods to do a GUI capture record, then playback. Test tools tend to store the captured data in two formats (ie -files) simultaneously. One is human-readable (like C code) the other is stored in an ascii file to represent the winsock hex data that was passed during the transaction. The winsock hex file is not obvious to the user as it happens under the covers of the GUI. These two files are used simultaneously by the test tool during playback to simulate a transaction of some type. It is also important to note that the concept of 'buffers' are used in these files to hold a certain amount of data - usually corresponding to a gui click.
The problem occurs while performing a capture on a program if the data captured in the winsock hex file had unique data in it - this could be in the form of session ID or other. During playback, the test tool would fail because during record it had captured only the one session ID, however while repeating during playback, the program being captured wanted another session ID. Hence a failure because the data passed to the program was not expected by the program therefore producing an unwanted result.
The process solution is as follows: 1. do a capture record on your application twice 2. do a file compare on the two hex winsock files created (one per capture) 3. note which buffer in the winsock fil...