Testing the Tester’s Pulse!

Height of frustration when our “Project Manager”/ “Team Lead” ask the following statements.

1. Are you sure, you have tested and verified the functionality?

2. Speed up and complete the sanity/regression testing soon as we need to push the latest code into the production instance.

3. It’s just a ‘Change Request’, it will take an hour to test those changes.

4. Guarantee me that, there are no bugs in this tested build.

5. I have a Client Demo within an hour/today, so just have the tasks done. Need this to be in live within the specified time-frame.

6. Are you bored on testing this application repeatedly?

7. Come on/ Plan for Saturday, Sunday or Holidays to test the application.

8. I didn’t have time to read your bug report. Just examine by yourself and close it.

9. Close all the bugs today itself and give an ideal defect report which provides a clear info. (Instead of using the term Testing.)

10. Kindly communicate with developer team and plan accordingly for all the bugs you have posted on Defect reporting tool.

Agile Methodology

1. Delivers the maximum business values early on in the project.

2. Promotes customer happiness.

3. Provides customer driven approach.

4. Spotlight on the speed of delivery.

5. Provides frankness and visibility to customers.

6. Removes obstacle in a prioritized and systematic manner.

7. Improves employee maintenance by empowering employees and by promoting self-management, team communication, learning, and value-building.

image courtesy: Google

Test comrade in "Google" Search

Searching on "Google" for “Test comrade”, it goes for “You Failed Your Math Test, Comrade Einstein”. I’m happy to see Einstein’s name when my blog name was searched.

Top Link(in Google) for the text "Test comrade" is:

Test comrade

Usecase Format and Example!!!

Usecases for the {Functionality Name}
--------------------------------------

UseCase Name: [Give a reasonable name for the usecase.] [Usecase Id]
[Sample Format >> Tab-name_functionality_Report] [Sample Id >> (UCTNFR001)]

Actor: [The users who are going to operate the product/application.]
[Sample Actors >> New User/Vendor/Manager]

Assumption: [Assuming the actor would have done those steps to execute this use case.]
[Sample Assumption >> User is a registered user.]

Description: [Precise synopsis about the functionality.]
[Sample Description >> Adding the item(s) in the shopping cart. {Present Tense}]

Steps:
[Steps to complete this functionality (don’t include the assumption{s} in the steps.)]
[Sample Steps >> {Present Continuous Tense}
1. Actor adds an item with cart ID, item ID and quantity.
2. System checks if the inventory is enough.
3. System updates the inventory level.
4. Updated shopping cart contents and total price are displayed.]

End state: [Need to put in the picture like Actor finished that functional procedure successfully.]
[Sample End State >> User adds item{s} to the shopping cart.]

The below list is an extra to a normal Use-case;

Negative Flow: Apart from the primary flow/primary steps, if there is any Wireframes(if available both for positive and negative flows) & negative steps; that can also be mentioned. 

[Sample Negative Flow >> If user clicks on 'Cancel' button, then application navigates to Home page.]

Note: Make sure the flow/steps is complete/sensible when other than you reads it.

Epitome of Testing

For those who are not familiar with the word ‘Epitome’, it’s nothing but “Essence”.

As a person in a QA/Tester role there are a number of typical roles that can be approved.

• Sheriff – Bringing order to the Wild West. Chaotic development processes are roped in and consistency and discipline instilled in the vacuum.

• Cheerleader – Pumping the team up to be more than they are. ‘Better unit tests? Way to go’

• Cop – More or less the opposite of the Cheerleader. While typically you get more flies with honey, sometimes you do have to bring out the vinegar.

• Negotiator – An active role in figuring out the trade-offs between development and test.

• Marketer – A longer-term variation of the Negotiator which uses more subtle techniques for furthering agenda.

• Coach – Strategist and morale support.