Sign up in 30 seconds.
No credit card.
No risk.
Free forever.
Just try it.
Delete page: Load Testing Questions
You need to know how the system will be used. Ask plenty of questions of project stakeholders and write down the answers.
- Will it be mostly for anonymous browsing?
- Is it designed for internal company research?
- Does it primarily facilitate collaboration between trading partners?
- Are there planned marketing campaigns to promote the site?
- B2B or B2C?
- Will employees all sign-on at the same time each day?
- Are there regular times of higher usage such as end of month?
- Can irregular events such as webinars or advertisements drive waves of traffic?
- How many people does the marketing department anticipate coming to the site monthly? Daily?
- Does the user interface serve as a front-end to non-integrated back-end system such as PeopleSoft or a CRM?
- Is single sign-on or other identity access management system involved?
- How fast should a page load?
- What response time would the CEO consider acceptable to her/him?
- Does the VP of Marketing have any idea of the correlation between site performance and revenue?
- How does the executive team define success for the average response times of this application?
- Has our development team built this app from scratch?
- Are any open source modules being used?
- What is the primary technology stack? LAMP, MS, other?
- How many coding languages are we using? Which ones?
- Which database engine is deployed? Oracle, SQL Server, mySQL, other?
- Are we hosting this in our own center? Co-located? Dedicated hosted servers? Cloud?
- What are the logical layers in our architecture?
- What are the physical layers in our architecture?
- How, if at all, are we configuring load balancing?
- Is caching turned on in the application? Web server? Database or messaging?
- Does the web server use a compression technology? Is it turned on?
That's just a sample. The idea is to get a broad context of which the system will operate. Ask! Listen! Take notes!