Characteristics of a good Performance Tester by Chris Jones:
Original Article Link- Always look for boundaries: Do they always ask, what if? Have you tried..? Often Performance Testers actively play Devil’s Advocate when no one else does. They actively look for ways to break things and think creatively to cause issues.
- Be “technical,” and a coder at heart: Regardless of their background, they must question things at a technical level. Not necessarily from a development background, they often find themselves “coding” solutions to technical problems or finding better, automated, easier solutions, perhaps using macros, scripts, spreadsheet formulae or another technical wizardry. They love to tinker.
- Have a broad understanding and knowledge of IT: They might be from a particular background or specialisation area, but they need a good understanding of how things work and fit together. They might be a programmer, but have an understanding of networks, security, architecture, etc. Or maybe a functional automation tester with knowledge of system architectures and an interest in security. The key is broad knowledge – deep in some areas – enough to know how, why and when things interact.
- Have a deep understanding in their area of specialty: Having said they need a broad understanding of IT, a good Performance Tester must have deep understating in their area of speciality. In the OSI model, I’d expect specialisation in (at least one of) the physical, data, network, transport, session, presentation or application layers. Alternatively, they could have a deep understanding of testing processes and/or programming.
- They aren’t afraid to look deeper: Even though they may not have complete information for a full solution, they know where and how to go about finding it. There may be gaps in their knowledge in places, but they’re not afraid to investigate and correct that. They recognise where these gaps are. They are able to quickly find out how things work, and sometimes do so just out of curiosity. They’re not afraid to ask questions, and not only why, but how.
- They are smart/ sharp/ quick: Often they see what the problem or solution may be very quickly. Often able to quickly sort through the noise to spot patterns. They find themselves picking up high-level concepts and techniques quickly. They are very much realists, not theorists.
- They are methodical: There’s little point in doing things haphazardly. If results can’t be recreated or documented systematically, then they are worthless. Good Performance Testers work methodically to a goal, never randomly. One thing builds on and leads to another, predictably.
- They think differently: When people think the same, their results often match. To break things, Performance Testers often have to think creatively, negatively and destructively. They think not in terms of business users, customers, technical programming or technical infrastructure, but often across and outside all of these. Performance Testers often are happy to be thought of as odd, unconventional troublemakers.
- They take ownership: Often Performance Testers work alone, using tools, skills and knowledge that cross technical boundaries within tight deadlines and at odd hours. Often that requires they “step up” and take accountability and ownership to get things completed on time. Being accountable for results and taking ownership is key. Performance Testers often have to deliver the bad news that others don’t want to hear.
- They are clear and logical communicators: As Performance Testing crosses many architectural, business and technical boundaries, Performance Testers need skills to be able to communicate well verbally, in written form, and visually with graphs/infographics. They need to be able to and comfortable with presenting results in front of technical, non-technical and management audiences. If no-one understands what the findings mean, the results are worthless.
- They like it when they break things: Lastly in my list, which brings things back full circle, as a Performance Tester, ultimately, they must enjoy doing what they do. And often that means breaking things with ingenuity, intent and sometimes, just because they can.
Date: 14 Jan 2019
Article Link
Date: 7 Jan 2019
Article Link
Date: 31 Dec 2018
Article Link
Date: 10 Dec 2018
Some time back I have shared an important article on microservices and it's architecture, to continue the same topic today, I am sharing another article published by Neotys on Microservices implementation in DevOps.
Article Link
What is DevOps?
DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.
Date: 3 Dec 2018
LinkedIn Article
DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support.
Date: 26 Nov 2018
Physical CPU vs Logical CPU:
Article Link
Date: 19 Nov 2018
Again, you are back to work and definitely feel either stressful or boring, so let's do a fresh start of this week. Why do not we discuss something new? Yes, sometime back I tweeted and listed many cloud-based performance testing tools. Under the same category, a new tool has been born named "PerfMeter". As of now, only beta version of PerfMeter has been released, so if you think to use this online performance testing tool, verify your test result before publishing to the client. You can get more details on the same by referring to below link:
List of some useful tool which supports mobile application performance testing:
- LoadRunner
- JMeter
- Sauce Labs
- TestComplete
- WebLoad
No comments:
Post a Comment