6/20/2023 0 Comments Neoload testing sample resume![]() It is the responsibility of Performance Test Manager/Lead to get the essence from the customer. He needs to play the role of a mediator who bridges the gap between the novice user language and performance testing terminologies. A Performance Test Manager/Lead needs to spend his time to understand the client’s expectation by asking the right set of questions and transforming the conceptual requirements into quantitative goals. In most of the cases, the non-functional requirements are either defined incompletely or they are more conceptually rather than quantitative. “How to get the performance requirements from a non-technical customer?” This is a valuable question that everyone has. Once all the non-functional requirements are finalised and he gets the testable NFRs then these NFRs should be properly documented in the Non-Functional Requirement Document and get the approval from the project stakeholders. There is also a high probability not to get clear and reasonable requirements in one meeting so he needs to set-up multiple meetings with the project stakeholders. He may get the requirement in layman term which may require thorough study and deep analyse to extract the testable NFRs. Once the performance testing scope is finalised in the risk assessment phase, then either of them (Performance Test Manager or Lead) has to schedule a meeting with the project team to understand the client’s expectation. Performance Test Manager or Performance Test Lead has a responsibility to collect, discuss and finalise the Non-functional requirement. The end result of this phase provides quantitative NFRs which helps to prepare a correct workload model during performance testing. All the requirements are documented, categorized and concluded in the Non-Functional Requirement Document. To collect the requirement, analyse them from performance testing perspective and finalise the quantitative NFRs all these steps fall under the NFR gathering phase of PTLC ( Performance Test Life Cycle). The project team or client sets the expectation for performance testing in the form of non-functional requirements. For example: If 1000 users hit ‘Account Balance’ link at the same time then the application must respond to all the users within a defined time (say 3 seconds). On the other hand, the non-functional requirements are oriented to the performance of the system in terms of responsiveness and load-bearing capacity. For example: If a user uses a banking application and clicks ‘Account Balance’ link then the application must display the correct balance available in his account. The main difference in functional and non-functional requirement is that functional requirements are end-user result oriented and stressed over the correct output. Difference between functional and non-functional requirement: whereas some of the goals are load bound like real-world user load, throughput etc. ![]() In non-functional requirement, some of the goals are time-bound like the response time of a page, request per second, resource utilization etc. The number of requests processed by the application per unit time.The number of users handled by the application.Some simple examples of Non-Functional Requirements are: Since PerfMatrix is a core performance testing site, so non-functional word will be specific to Performance Testing only. It is a combined requirement for all types of non-functional test. Non-functional requirements are the testing goals which are created especially for performance testing, security testing, usability testing, etc. ![]() What are the Non-Functional Requirements? ![]()
0 Comments
Leave a Reply. |