How much are you ignoring?

Not only in software testing, not only in profession, not only in personal life but the whole day. I am specifying the whole day only. Do you know how much we testing things? Do you know how much we are getting knowledge? Do you know how much are we noticing? Do you know how much great idea we are discovering?

Now ask all those questions to yourself. Keep asking, getting some answers? If you getting a bit then you will know actually how much actually do we ignore everyday. Day by day, week by week, month by month, year by year.

You people will think what I am talking about? Is it really concerning about Software testing? or Application testing? or anything testing? Then I must say, ask yourself. Am I really not making sense?

For software testing, or any profession or any personal issues it is very very very important to track down how much we are knowing everyday, how much we are noticing and how much we are everything. Because ignoring is a very expensive thing to do, do we really can effort it?

What should be my agenda?

- Finding all the bugs or at least most of it?
- Comparing with standards or oracles?
- To seek client satisfaction?
- To find out application limitations?
- To make sure that application will not crash in some particular scenarios?
- To improve programmers work?
- To ensure user satisfaction?
- To make sure my application have something more to offer than other existing ones, or it is more reliable?
- Or it is all of them, or even more?

And I need to pick what it will be and what more should I ignore.

Jmeter for Load and Performance testing

Jmeter is a very well known tool for load and performance testing. Installed it today in my ubuntu environment and it is working fine :) Thanks to these two following links.

Installing Jmeter -> http://joysofprogramming.com/install-jmeter-java-ubuntu/

How to use Jmeter -> http://www.roseindia.net/jmeter/using-jmeter.shtml

More about Jmeter -> http://jakarta.apache.org/jmeter/

Although Jmeter is popular a lot but I guess this post is gonna be useful for some ppl, like me ;)

Project feedback

After finishing my working project within given deadline, I was asked to give feedback about the project and people worked in the project. As this was mine first time in Agile I was nervous and confused. Because first of all I have to give a general assessment about the application and about programmers. Maybe this is the trickiest part of being a software tester.

My coordinator asked about programmers one by one, what I am supposed to say? The truth? Man truth will hurt :P I will work with them on the future again I know. Although management is saying everything is confidential :( But what about bureaucracy? So, I highlighted noticeable mistakes they have done and hide others. Tried to sound reasonable. The summary was "I enjoyed very much working with the team".
But now I realize I skipped so many things, lets save it for the next run :)

Now the next question comes about the project :) I applied Lesson Learned from Software Testing dialogue "Within my test cases the application did not fail". And for this section too I will add so many more things no the next run.

Lets see how much I can improve myself in the next project. Wish me luck :D

The HelpMan

To be honest I have always take my profession as a reporter. A very specific, to the point and brief reporter about the application or solution I am testing. But after start working in Agile my believe changed. Now I see I am helping programmers to improve their code(although they are very angry for this help all the time), I am helping the manager so the project can finish on its deadline by taking hot talks of programmers coolly and professionally ;) and I am helping the product owner so he can have satisfied customer so money can come smoothly and last but not the least people who do maintenance part, whenever a problem arise I can help to inquiry what the exact situation is and where to look for the solution. So I am really The HelpMan :D

P.S. Instead of Helper I say The HelpMan because it sounds cooler :P

Being nightmare for dev's

Most of the project management want us (testers) to be the nightmare for dev's (developers/programmers), but I do not agree with them. According to me it hamper the schedule of project. What we really need to do is to be the best friend for developers, may be they will not accept us our work intends to criticize their work. But we should intend to support them, as I learned Quality comes from dev's.

App Chain

Recently I found a bug in my working project, after proper investigation it seems the bug was not in code, it was in another application that we are customized for this working project. I will not name that application we used in our project but it is big and it is a really good tool to use but using buggy tools in your app make your app buggy.
So, be very careful about what app you are using to develop your app, beware about the chain of bug ;)