Future of Performance Testing in Robotic Field. What would be your way forward plan?
Article Link.
Date: 16 Jan 2019
Article Link.
Date: 16 Jan 2019
Let's have some facts about what could be the wonder may happen in the year 2019 in Performance Testing World. This post may guide you to choose the specific area of your interest in PT domain.
Article Link.
Date: 2 Jan 2019
Alexander Podelko, a well know personality in performance testing world. I like the way he explains the performance testing stuff. Luckily, I found his one of the finest document in which he described the PTLC term by dividing the things into small parts. Although you are a performance testing expert, read this wonderful document once.
Document Link.
Date: 26 Dec 2018
Cached data is nothing but files, images, scripts and other media files stored on your devices by the website or app. Data is stored on your devices in a reserved space, so the next time when you are visiting the app or website, information is already available. Cache plays an important role in Performance Testing World. Because to improve the application's performance cache helps a lot! How? Read the LinkedIn article shared by Deepanshu Mittal:
LinkedIn Article Link.
Date: 19 Dec 2018
Identification of performance bottleneck is an art and how a performance tester can enhance his/her skill to identify the bottlenecks is very well articulated by Scott Barber. Read this article to know what are the usual performance bottleneck and how to detect them.
Article Link.
Date: 12 Dec 2018
1. Performance requirements—criteria that are absolutely non-negotiable due to contractual obligations, service level agreements or business needs. Only those criteria whose sub-par performance would unquestionably lead to a decision to delay a release are absolutely required.
2. Performance goals—criteria desired for release, but negotiable under certain circumstances. For instance, if a response time goal for a particular transaction is set at 3 seconds, but the actual response time is determined to be 3.3 seconds, it is likely stakeholders will choose to release the application and defer performance tuning of that transaction for a future release.
3. Performance testing objectives—items that add value to the team through the process of performance testing but are not intrinsically quantitative. For example, one objective might be to provide certain data to systems administrators to assist them in tuning systems under their purview. Another objective might be to determine peak application usage that the existing network can support.
The above content has been taken from a white paper "Get performance requirements right - think like a user" written by Scott Barber and published by Compuware. The reference document can be accessed via this link.
Date: 5 Dec 2018
Neotys who is famous for conducting the event on Performance Testing and Engineering; has published a very fine article on mobile performance testing. They have shared 7 tips which are worth to read before commencing mobile performance testing.
Article Link
Article Link.
Document Link.
LinkedIn Article Link.
Article Link.
Date: 12 Dec 2018
2. Performance goals—criteria desired for release, but negotiable under certain circumstances. For instance, if a response time goal for a particular transaction is set at 3 seconds, but the actual response time is determined to be 3.3 seconds, it is likely stakeholders will choose to release the application and defer performance tuning of that transaction for a future release.
3. Performance testing objectives—items that add value to the team through the process of performance testing but are not intrinsically quantitative. For example, one objective might be to provide certain data to systems administrators to assist them in tuning systems under their purview. Another objective might be to determine peak application usage that the existing network can support.
The above content has been taken from a white paper "Get performance requirements right - think like a user" written by Scott Barber and published by Compuware. The reference document can be accessed via this link.
Article Link
Date: 28 Nov 2018
Performance Testing Planning is an important phase PTLC. During this phase, you plan a roadmap to drive the performance testing and prepare a strategy to conduct the test according to the requirement. Many people ask to provide a Performance Test Plan template so that they can document all the testing related stuff, crucial pointers, approach and stakeholders. Today, I have list out important headings which should be covered in the performance test plan. You can refer these heading and prepare a test plan by yourself.
1. Cover Page
2. Table of Content
3. Project Overview
4. Application Architecture
5. Signed-off NFRs
6. NFR and NFT Matrix
7. Performance Test Approach (including the goal of each individual test, entry and exit creteria)
8. Test Environment and scalability %
9. Test Data
10. Risk
11. Assumption
12. Issue
13. Dependency
14. Project Plan and Timelines
15. Non-Functional Testing Timelines
16. Non-functional Testing Team member contact
17. Test Plan Sign-off stakeholders
18. Record of changes
19. Acronyms
20. Glossary
21. Referenced Documents
Article Link
Date: 14 Nov 2018
Last Friday, I have shared a post related to how quickly you can set-up Dynatrace and start monitoring AWS based application. Continue with the same tool (Dynatrace), today I am sharing a post stating the advantages of Dynatrace. Must read. Refer the link:
Article Link
Dynatrace is a powerful monitoring and profiling agent-based tool. It is widely used to identify the bottleneck and carry-out deep root cause analysis up to code level.
Related Topic:
No comments:
Post a Comment