I have seen people coming back and asking what should they test ??
Yes, these are essentially people with less exposure and experience but the fact is that its them who get confused !!
An experienced tester would immediately comment .......EVERYTHING !!
So coming back to the core question what should you test ??
The BlackBox perspective .....
Any sofware would have certain madatory fields and certain non madatory fields on the user interface.
I am not taking any part of usability testing into consideration here .....
Friday, March 16, 2007
Wednesday, March 14, 2007
Saturday, March 10, 2007
Confusion ....tester = QC ? or QA ? ...something else
Hmmmm.......
for some good time now, I've been seeing confusions in people regarding who is a tester ..... Some people percieve that tester is a quality control person ........some think they are quality assurance persons ........ the list is slightly more bigger, but these two are the main confusing roles ......
Why can't a tester be percieved as tester ? .....why cant he be percieved as someone who knows how to break the code ........ oh !! not another confusion ......... i am not talking about a hacker here but a tester ........
You may agree to differ in opinion but honestly that is what a tester does .......his job is to build scenarios, create plans, find testcases, generate testwares .......and test .........
White Box testing experts get in to delve into the structural aspect of the code and Black Box testing experts want to understand the acceptance levels of the software ....... with the client/ customer perspective.
Oh !! how did I forget to add ......a biggest misconception that failed developers become testers .....
Does the argument finish here ......... NO... wait to hear more on this blog !!
for some good time now, I've been seeing confusions in people regarding who is a tester ..... Some people percieve that tester is a quality control person ........some think they are quality assurance persons ........ the list is slightly more bigger, but these two are the main confusing roles ......
Why can't a tester be percieved as tester ? .....why cant he be percieved as someone who knows how to break the code ........ oh !! not another confusion ......... i am not talking about a hacker here but a tester ........
You may agree to differ in opinion but honestly that is what a tester does .......his job is to build scenarios, create plans, find testcases, generate testwares .......and test .........
White Box testing experts get in to delve into the structural aspect of the code and Black Box testing experts want to understand the acceptance levels of the software ....... with the client/ customer perspective.
Oh !! how did I forget to add ......a biggest misconception that failed developers become testers .....
Does the argument finish here ......... NO... wait to hear more on this blog !!
Scenarios in Product and service industry
In a service company scenario you do not own the source code under any circumstances nor the test (plans/scenarios/cases ) etc. You do it for a client who has outsourced these jobs to you. The ownership for all this eventually lies with the client and you have to share it back with him. This will be dependent on the statement of work agreement with the client.
In a product company scenario, source code along with all test related documentation is owned by the company itself. They may or may not share it with the customer of the product. Sharing will be highly dependent on the business need.
In a product company scenario, source code along with all test related documentation is owned by the company itself. They may or may not share it with the customer of the product. Sharing will be highly dependent on the business need.
Subscribe to:
Posts (Atom)
Posts
