Skip to main content

Introducing my blog - Numero Uno!

Caution!
What you are about to read in this blog may help you improve your knowledge of software testing & quality assurance and may help you:
  • Learn about people management best practices 
  • Become a better leader
  • Know more about software testing in general and in depth
  • Become better at functional testing
Welcome to my blog, where I spread the contagion of quality in everything - software, electronics, people, marriages and life. And I am Savio Saldanha - a certified Project Manager and Software Tester.

Over the years (which are quite a few), I've observed that people (including myself), increasingly, tend to possess shorter attention spans, shorter than those of a goldfish! So, here's some help: Read through if what you're reading interests you; skim to the end to know what and how you can learn from this blog;
In any case, submit your email address in the box to the right of this post and allow me to send you emails about latest in leadership and trends in software testing.

In my quest to improve the world I see, I've decided that my first step towards that goal is to help you improve the quality of your leadership & management and the software that you are associated with. As we progress, we'll talk about the various factors that comprise great workplace leadership and factors that go into making a good quality product. And so, we will discuss, at length, the following:

Leadership and management:
  • The traits of a great manager
  • Transform management into leadership
  • Keeping your team pumped
  • Benefits of good leadership
  • The deadly sins of someone in a leadership role
  • How to spot a bad manager
  • The consequences of poor leadership
Software Testing:
Being the last phase in an Software Development Life-Cycle (SDLC), software testing tends to be the most abused phase in the entire development cycle. This being the case, the design of a Software Test Life-Cycle (STLC) should accommodate the various intricacies that comprise software testing in order to identify time consuming activities during testing, reduce the time taken by the STLC, reduce the number of leaked defects, and increase confidence in the application under test (AUT). 

As the world moves towards ~70% automation of testing by 2020, please join me in envisioning the future - 100% test automation.

Till then, learn with me:
  1. Test Methodologies and Techniques
  2. Test Process Optimization
  3. Test Tools
Besides testing software, testing a company's culture is something that interests me. 

Stay tuned; And I wish you all the very best in being a great leader and the best tester around.

Also please note that my team is available to undertake software testing assignments. You may reach out to bureauofquality@gmail.com with your needs.

Cheers,
Savio Saldanha
Labels:

Comments

Post a Comment

Tell me what you think

Popular posts from this blog

3 Common mistakes that testing teams should avoid

A friend and I were recently talking about the kind of common yet critical mistakes that are made quite unknowingly during the test phase of the SDLC. Some of the points mentioned below are the kind of processes mandated by companies for ages! It is not uncommon to see that test managers, along with the test leadership within companies making such blunders. And if you see such practices being followed at your company, let them know that they should be ridding themselves of these common mistakes. 1. Test cases are not traced back to the requirements One of essential artifacts of the testing phase is the Requirement Trace-ability Matrix. What this matrix does is help you link your requirements to your test cases. As a result, you would be aware of the coverage your test cases provide to your requirements. Not having an RTM puts you and your team at the risk of coming up with an incomplete coverage of the requirements  and the possibility of leaking defects. Her...
1 comment
Read more

A quick guide to writing better test cases

This topic has been touched many times over on the internet; I'll leave out the advise of keeping simple, your test cases and the language of your test cases. Without going into methodologies and techniques used in testing, I'd like to outline a few principles of test case writing that you should bear in mind the next time you're writing test cases. 1. Design scenarios Firstly, don't think of writing test cases.. :) Or anything related to test cases. For the particular application / unit under test (AUT), take time to think through and identify possibilities of: Inputs - All possible inputs that can be given to the AUT. Your inputs can be data or a certain action to be performed, like clicking a button Outputs - All possible outcomes / behaviours of the AUT in response to the input  Trigger points - Conditions that when activated, cause the AUT to perform certain action(s) Alternate flows - When testing workflows, always ensure you identify flows other than t...
Post a Comment
Read more

Attention! These 3 Activities are Slowing Down Your Testing!

These are activities you perform almost daily. You're tired of the monotonous work involved and yet its hard to realize that these are the activities that you must optimize in order to speed up your testing process. You would probably have these at the back of your mind.. Let me help you bring them to the fore! 1. You derive your test cases from a requirement document: We're all faced with this situation each time some piece of code needs to be tested. We look for the requirements, and frame our test scenarios and test cases. Have you ever thought what exactly are you doing by writing test cases? You're simply rewording the requirements! Something simple for example: Requirement = The login page will allow system access to the user by authenticating his/her username and password. The user will be allowed to enter the username and password through text boxes of not more than 20 characters (this does not mean the data type char). Test Case#1 = Verify the presence of ...
Post a Comment
Read more