+

Search Tips   |   Advanced Search

  • Previous Topic
  • Next Topic
  • Book Index

    • Push frameworks

    In This Section

    1. Context
    2. Definition
    3. Modified User Paths
    4. Frameworks

    See Also

    1. Design
    2. Record a test scenario
    3. Update recorded content
    4. Open a NeoLoad project
    5. Servers
    6. Authentication
    7. User Paths
    8. Web pages
    9. Requests
    10. Logical actions
    11. Advanced actions
    12. Frameworks
    13. Shared Containers
    14. Populations
    15. Variables
    16. Search and Replace
    17. Flags
    18. Service Level Agreement (SLA) profiles
    19. Import and export a project
    20. Export a project for NeoSense
    21. Design collaborative projects
    22. Check the sanity of a project at design time

    Context

    Push frameworks are used when testing applications that use Push technology. This is a type of communication in which information is pushed by the server towards the browser, contrary to the normal Pull principle whereby the browser initiates the request for information.

    Definition

    Push frameworks can be used to automatically create User Paths that are compatible for use in a Push environment.

    For an application to operate in Push mode, a Push channel is required through which the data is fed from the server to the client. Handling the Push channel requires special tools and concepts specific to this particular type of application. Each framework allows creating User Paths, after recording, that take into account the Push channel.

    How it works:

    1. During the recording, NeoLoad detects that the recorded application is using a Push framework.
    2. At the end of the recording, NeoLoad offers to create a modified copy of the User Path that has just been recorded.
    3. This User Path is named <original name>_<framework name>.
    4. This copy contains all the changes specific to the detected Push framework and that will help easily design the User Path and enable a playback as realistic as possible.

      The User Path tree contains now two User Paths:

      • the original User Path containing the raw recording data. This is a potential source of data for developing the User Path actually used. It may be deleted at any time.
      • the NeoLoad-modified User Path. You are strongly advised to use this User Path as a basis for ongoing design.


    Home