The PushToTest Engagement Model
PushToTest uses a professional and agile engagement model to provide your organization with effective and rapid service.
The PushToTest engagement model is unique in that it builds your test and ends with you having test results in-hand and unlike other service providers, we leave the test behind with your team trained on how to build their own tests.
"Our previous testing service would only go as far as writing the first test script as an example of how to use their system, and only as a favor to us. PushToTest would not abandon its customers like that."
The PushToTest engagement model in detail:
- Analysis of your application development environment begins with our experts reviewing your software development process, current challenges, and your team's expertise and limitations. PushToTest usually puts 1 to 3 of our experts on-site for 3 to 5 days. We deliver a test plan document to include critical business flows and user archetype definitions, with sections on vulnerabilities, resiliency, physical, logical, database, and network security.
- Proof Of Concept builds a fully working test of your application. PushToTest usually conducts the test development work at our facilities with frequent conference calls, email messages, and Web desktop sharing sessions with your team, especially with your Subject Matter Expert (SME.) This usually takes 5 to 8 days. We deliver a set of test scripts, the TestMaker environment, and operational test data.
- Test Operation uses the delivered test to identify performance bottlenecks and broken functions. PushToTest uses the analysis team to identify the root cause and recommend steps to mitigation of performance and functional problems. This usually takes 5 to 8 days. We deliver a results analysis and mitigation document for your team's action. PushToTest usually puts 1 to 3 of our experts on-site during test operation.
-
Training and Ongoing Support uses PushToTest's support desk through phone calls, email, and instant messenger to respond to your team's questions.
The analysis captures and identifies many facets of your application and environment:
- Acquire IT infrastructure information including software development practices, testing practices, and operational service level requirements.
- Capture user and parameter data for the test, and analyze raw data into business flows, including use cases, data formats, protocols, components and patterns.
- Identify and determine critical processes and the technology that supports those processes, including concerns, vulnerabilities, and broken functions. This results in a definition of goals and success metrics. For example, number of hits per minute, concurrent user counts, and definition and number of tests to run.
- Formulate recommendations and comments, including determining ability to create events, notification for critical processes, and risk mitigation. For example, PushToTest provides expert opinions on what are good, bad, and questionable.
- Present findings to your staff and management. This can be in roundtable, interactive, or executive presentation format.
As an example, here is the engagement model we used for one of our recent customers:
-
Week 1: Test Definition and Business Flow Finalized
Operational data collected and tables populated
Business flows recorded into scripts -
Week 2: Test environment and load generation equipment installation
Calibration testing (identifying scalability of load generators)
Test Component development (identified in analysis) -
Week 3: Test Operation and Results Analysis
How did the test go against our success metrics?
How many users does the system support?
How much hardware do we need? -
Week 4: Team Training
Rerun specific tests
Executive reports and operational documentation
PushToTest responds to your exact needs by identifying the project goals, experts needed, training for your team members, and operational test data. We provide a price proposal that includes all of the above.
Introducing a new service from PushToTest Global Services: RapidPlan. RapidPlan is a bridge from our normal TestMaker training to a hands-on implementation of a load test. RapidPlan is a day-long event that happens after training the technical team, it brings management and technical teams together.
Consider the following:
- Training - TestMaker fundamentals, presents Tutorial Modules, using blackbox test techniques
- RapidPlan - Brings the technical team and management team together. Transitions from what the technical team learned in the Training to developing a plan with the management team on how to apply this knowledge. Identify the goals to measure, system use, forecast use. Plan the next steps (test use cases, sizes, goals). Deliverable: Test plan document.
- QuickStart - PushToTest experts build your first test, operate the test, and provide root cause analysis assist with mitigation, and jumpstarts your team in building their own tests. Provides hands-on implementation of the goals defined in the RapidPlan, prepares Sprint team members to run a load test. Develop each type of test. Do some functional and load Test Operation. Understanding Results Analysis.
