Skip to content
  • About
  • Home

Performance Testing

Exploring Nonfunctional Testing

  • About
  • Home
  • Toggle search form

Five habits of good engineers

Posted on 19/04/202319/06/2023 By lefty No Comments on Five habits of good engineers

Things I learnt from people who are much much better engineers than I am:
– Take notes. Always. Take detailed notes and keep a record of everything you do. Keep manual logs as well as automated logs if you can. Keep your logs organised by year and project.
– Take a video of your first testing session on a new system. Some of the things will not be reproducible, but you’ll have proof that they did happen.
– Ask kindly. If you think you found a bug, talk to the developers, team leads or whoever is concerned. Show it to them. Ask them what they think. Ask them to explain what may be happening. If you talk to them first, no ticket you write will ever be rejected. They will thank you for it, for writing it down on their behalf.
– Tickets make risks visible. It is okay to receive a promise that it will be fixed. And it feels good when it does get fixed. But bug tickets bring risks to a visible level. They raise them to a conscious level within the organization. Always write a ticket, no matter how trivial an issue may seem.
– No database migration is ever smooth. No matter how confident the DBA, the chief something of something important and the FBI are about it, a DB migration is always highly risky. It may cause hours, days or weeks of outages. So if you are testing for it, no amount of preparation and care is too much.

Performance Testing Tags:Musings

Post navigation

Previous Post: Leistungstests vor der Markteinführung – Technischer Leitfaden (Was ist zu testen, wie ist zu testen und wie sind die Ergebnisse zu interpretieren)
Next Post: Industry Benchmarks for Performance Testing – Lessons from High Frequency Trading

Related Posts

My biggest failure as a tester Performance Testing
We’re rollin’ Performance Testing
Three things they don’t teach you at Uni about testing Performance Testing
Benchmarking and Metrics in Performance Testing Series Availability Testing
Ensuring Software Testers’ Impact Business Performance Testing
One thing I always do when testing user input Performance Testing

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Benchmarking and Metrics in Performance Testing Series Part 2
  • The Importance of Stakeholder Management in Pre-Launch Performance Testing
  • Ensuring Software Testers’ Impact
  • Industry Benchmarks for Performance Testing – Lessons from High Frequency Trading
  • Five habits of good engineers

Archives

  • June 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023

Categories

  • Availability Testing
  • Benchmarking
  • Business Performance Testing
  • Load Testing
  • Performance Testing
  • Performance Testing Methodology
  • Rapid Response Testing
  • Robustness Testing
  • Stakeholder Management
  • Technical Performance Testing
  • Volume Testing

Copyright © 2026 Performance Testing.

Powered by PressBook Masonry Dark