Abstract: A system and method of generating information regarding an application designed to be used over a network can be used for parsing the code of the application into its various components and determining relationships between the components, which make up the code. The code of an application can be analyzed to determine which components of the application are transactable and which are non-transactable. Furthermore, contextual and cross-contextual relationships between the components and the code of the application may be defined. The components can be portions of a document, which can in turn be part of a larger application. Information regarding the components of the application, and therefore the application as a whole, such as the functionality/performance of components and component relationships, can be determined and may be posted to a data store for later retrieval and processing.

Abstract: A process can generate prospective information regarding application. In one example, rendered source code for the application could be received by a client computer from a server computer. The process can comprise retrieving data regarding historical information for the application and generating prospective information regarding the application based at least in part on the historical information. Examples of prospective information can comprise scenario modeling, predictive analysis, forecasting, scalability estimation, combinations thereof, derivations thereof, or the like. In many embodiments, the process can further comprise parsing the application to identify components within the application. At least some of the components can be part, but not all, of a document. The process can still further comprise testing the components to generate the historical information for the components. The profile construction and analysis may be performed for a group of applications.

Abstract: A process can be used to test an application. In general, the process can include a transaction definition portion, a validation portion, and an optional modification portion. Unlike the conventional processes, the testing can be performed using “scriptless” transactions. The transaction definition may occur during navigation by a user through a network site while data regarding application is collected. Alternatively, a user may select transactable components or transactions from a list or a group of icons. In still another alternative, the transaction definition may be performed automatically using log files or component relationship data. Validation may be performed in-process or out-of-process to give greater flexibility. Modification may be performed manually or automatically. Also, modification may be performed after validation has started but before it is completed.