Friday, December 16, 2011

Factors to consider during regession testing

I read an interesting material on regression testing here.

Few important point regarding regression testing on which we should focus is as follows:

  • Test fixed bugs promptly. The programmer might have handled the symptoms but not have gotten to the underlying cause.
  • Watch for side effects of fixes. The bug itself might be fixed but the fix might create other bugs.
  • Write a regression test for each bug fixed.
  • If two or more tests are similar, determine which is less effective and get rid of it.
  • Identify tests that the program consistently passes and archive them.
  • Focus on functional issues, not those related to design.
  • Make changes (small and large) to data and find any resulting corruption.
  • Trace the effects of the changes on program memory.

Thursday, June 16, 2011

Excellent Video to learn Scrum

Please find excellent presentation to have an idea about SCRUM-Agile Software Development Methodology.

Saturday, June 11, 2011

Devise your Learning System

Few months back, in one of our team meeting, we tried to devise a learning system for an Organization/Individual, our program manager really gave his valuable thoughts and shared his wisdom, we summarized the proposed learning system at the end of the meeting as follows:
1. Decide what to learn?
i. What is easy for me to learn and easy for me to do?
It depends upon on the natural talent of any individual and one should choose his learning domain according to his natural ability and aptitude.
ii. What is hard for others to do?
We can select a field that can act as a competitive advantage for us.
iii. What is in demand and people are willing to pay for it?
We have to find the target market for the selected domain after market research.
2. Find, search, and collect the resources to learn.
i. Make directory structure for all your industry and organizational knowledge.
3. Formulate the learning material that suits your learning style.
4. Explore the material using your 7 multiple intelligences and 5 human senses.
5. Memorize the most important elements of the subject to master.
6. Use your knowledge in day to day activities at work; Test yourself by getting globally recognized certifications, and teaching.
7. Review your learning process to see how you will do it better next time.

Thursday, June 9, 2011

James Whittaker Presentation about Quality

There is an interesting presentation "Turning Quality on its Head" by "James Whittaker-Test Director at google", in which he did a comparison regarding where to spend money in order to improve the application quality, you can read the summary of his talk below:

Where to spend our budget ?
As per google, you do manual testing only when screwed up in the early development phases, and it is quite important to involve testers in the begining by helping the developers to write better lines of code in the early phases of projects. Quality is important to the world so the important question is to where we need to spend our budget, whether towards Testers side or Developers(developer oriented testing).

Argument to spend towards Developers side
1-You can not build the product and paint quality on it, so if you want to build the right product, you got to take the right start from the begining.
2-Cost of a fixing bug is 0$ while writting code, and it gets higher as we move along the phases like System testing, integration testing, crowdsource testing till dogfood process.

Argument to spend towards Testers side
1-If we want to involve testing right from the begining, we need to have dev like testers, that can help dev people to write code, and every line of code is a best possible line of code.
2-The most important bugs rises when we got the whole product ready, these are the bugs that can be faced by the users.and developers can not find these kind of bugs and testers add their value at this important stage when entire application gets ready.

Enjoy the presentation (Part-one) below:

Thursday, June 2, 2011

Eating your Own Dog Food

Eating your own dog food, also called dogfooding, is when a company uses its own products.
In 1988, Microsoft manager Paul Maritz sent Brian Valentine, test manager for Microsoft LAN Manager, an email titled "Eating our own Dogfood", challenging him to increase internal usage of the company's product. From there, the usage of the term spread through the company.
Dogfooding can be a way for a company to demonstrate confidence in its own products, and hence a kind of testimonial advertising. For example, Microsoft and Google emphasize the internal use of their own software products.
The idea behind "eating your own dog food" is that if you expect customers to buy your products, you should also be willing to use them.
Read more

Thursday, May 19, 2011

Present like Steve Jobs

Excellent video describing the key points of Steve's presentation



Enjoy and good luck for your new presentation.

Sunday, May 1, 2011

Importance of Build Notes

Few days back, I read an excellent article by “Dr. Vladimir Belorusets” about how to improve test coverage and avoiding missing test scenarios,
He mentioned quite useful points in this article in order to improve communication between Development and QA by establishing the process of accompanying each build with the Build Notes that briefly describe the changes introduced.
The following sections in the Build Notes can be added:
1. Changes in functionality
2. Changes in GUI
3. Code refactoring
4. Tests recommended by developers
5. Defects fixed
Here code refactoring means changing source code without modifying its functional behavior in order to improve code design and maintainability. As a result, regression testing is required since the developer can accidentally break the functionality that worked before.
In the same way, any ‘Changes in GUI’ may impact the existing GUI test automation scripts that are heavily dependent on GUI objects and their properties.

Friday, April 22, 2011

Tip of the day

Less Words, More Action

Thursday, April 7, 2011

Stay Hungry & Stay Foolish

Great speech by Steve jobs.



One speech with lots of wisdom.

Monday, January 31, 2011

Define Testers

“Testers are like lighthouses at sea shores, headlights of an automobile”
(James Bach)

Monday, January 17, 2011

Project Management Sin: Wastefulness

Wastefulness is like misuse of critical and important resources, and not allocation the right person for any particular tasks, it leads to:
  • Project Malaise
  • Loss of motivation
  • Loss of creativity (Doing same thing again and again)
  • Project Delays
One of the key for project success is to allocating the right resources.

You can read more about project management sins from here.

Project Management Sin: Pride

Pride is a believing that we know each and everything to build the product and deliver the prodit within timeline. it is expereinced when there is lack of stakeholders or lack of user involvement in the project, if there are no unbiased , indepedent stakeholders in the product, project will suffer:
  • Failure to solicite feedback
  • Failure to learn

Users stories in agile help to reduce communication friction between all stakeholders, and we can get continous feedback loop from our users and customers and keep ourself open to all improvements.

you can read more about project mangement sins from here.