This one is a very strong post I have been looking forward to share, but really never ever got the strength to do it. We Indians (with me as the 1st one on the list) are prone to get carried away and take things for granted. This is specially true with respect to the topic/subject line. Personally I think we received more than what we(associated to IT industry) deserved, and instead of thanking God, we started exploiting it.
Has any IT professional ever wondered how much he would be contributing to the revenue and then compare it with his salary.
Has anyone ever bothered to look on statistics that state that on an average 40% of the people who accept job offers do not join the Organizations. Maybe we do not realize, but mistakes are not spared in the kind of Industry we happen to be a part of. The country bleeds as a whole, and the signs have starting showing up.
In past over a decade I have seen so many Organizations shutting down as we as human beings have been having short-sighted visions and do not look the overall picture. But the time has come when even the good guys will also have to pay the price. When the mob starts, it does not recognize the color of the blood. No one gets away from consequences of karma, and in this case its the Nation which suffers at the end of the day.
Around a decade back, I was so impressed when I had heard right from the horse's mouth who had brought Motorola to India as he wanted to give something back to the country (was also one of the most down to earth guy I have come across in my lifetime). That particular BU had shut down (due to engineers like us), and today I feel ashamed even to contact such a great man. Forget about hundreds of people losing jobs (the good guys also).
I really wonder at times as to what kind of generations are we building. Do we tell our kids to be selfish in life, have short-sighted-ness, either leave nation or suck to whatever extent possible. Have no ethics, no values, no principles and basically dispute everything that's being taught in schools.
We definitely tell them about the political in-competencies, but do we tell them:
1. Narayan/Sudha Murthy have been running orphan-ages.
2. Sabeer Bhatia has been setting up schools and teaching poor children.
3. Sridhar Jayanthi goes to clean the parks wearing office unforms over the weekends (morning 5 o clock) with other colleagues. Without any show offs.
4. So many organizations have been running orphanages to old age homes contributing to whatever extent possible.
5. Pakistan media states that India has multiple heroes, but have we ever bothered to know who they are and how they happen to be. Have we told them that Azim Premji, Narayan Murthy, Ratan Tata, Anil Ambani and so many others are the most approachable-and down to earth people.
Tuesday, June 17, 2008
Wednesday, February 20, 2008
1. Testers Skill-Sets: Everyone wants to be a developer and not a tester, why? Because developers think that its a low skilled job. But testers knowledge skill-sets are very different and broad from development. It requires strong Operating Systems skillsets (including internals), databases, usability testing, scripting, networking, SDLC to processes compliances. Quality (CMM, ISO etc) and a lot more.
Problems with the Test Industry with respect to our subject: No tailored course and no specific benchmarking guidelines. All abstracts everywhere. But things have been changing, with certifications (both tools and engineering). Things hav... but not enough to convince everyone.
It calls for:
Fair insights into Operating System Concepts:
Scripting/Programming: Once I was interviewing a guy for embedded tools testing and I
asked him about the languages he's comfortable with for writing test plans. His answer was English. Is that wrong, i really do not know. I am referring to one of the world's biggest semiconductor company.
On the other hand, on a training session the trainer was referring to test scripts. And later it turned out to be simple English test steps. And this happened in one of the worlds best Security Org.
Bit of everything
Everything about 1~2 things.
Do I make sense???
2. Importance of FEVIFTTWH: Almost everyone I talk to refers to usability and
usability standards. But who defines it, and what is the standardization. Who sets
them, and how do they impact.
3. Has anyone seen an application with HWTTF....., ie, the menu starting from Help,
Window, Tools and so on from the Left Hand Side. Similar happens to be with all the
Usability/GUI's and more or less goes back to what Microsoft had implemented.
4. How would you define a bug that is least severity and still remains to be priority.
Has anyone come across any product by Microsoft that displays Win instead of Windows.
Bet you will not be able to find it as for Microsoft guys this would be priority 1
5. Measuring Quality: So how do you measure Quality. The simple answer is across what
is set as a standard that the product claims to be capable of 6. QA/QC: There cannot be any other term to start with especially with respect to our
subject. Hundreds and thousands of books/jobs/references/links/tutorials/lectures etc
etc that I have come across and each one talks about QA and not about QC/software
testing. I think the industry is yet to reach such a maturity stage where these terms
get defined. QA is a non technical job (a more of a process oriented targeted for
certification, in most of the cases, although proves out to be an umbrella activity
putting Software Testing under it, which is a pure technical job.
7. White Box Testing: And all the time, it reminds me of a continent about everyone
wants to talk about as much as they possibly can. And when you are told, or try to go
there everyone runs away like a thief saving for his life. Reason is simple, Whitebox
testing is nothing but a glass box testing, where in each and every
function/unit/module/subroutine..... is tested as per the coding guidelines specified. The only thing that a tester can do here is compliance checks with respect to the coding guidelines being followed or not. Having audits, incorporating comments and so on. Also this is true mostly for larger size organizations. For very small startups or thinengineering firms, multitasking makes more sense where the developers mostly do the development as well as testing.
8. Black Box Programming: Discussed earlier
9. Unit Testing—Is it white box or black-box: Lets do a File-->New in Microsoft Word. Is it a white box or a black-box. Before integrating various modules, it would be whitebox and when it gets integrated as a product, then it would be a black box, makes sense. In case it doesn’t, please do not curse me.
10. White Box Expectations from Testers: Since the time I started by career, hardly has any interview/conference/training/event happened wherein the said subject has not
been referred to.
Problems with the Test Industry with respect to our subject: No tailored course and no specific benchmarking guidelines. All abstracts everywhere. But things have been changing, with certifications (both tools and engineering). Things hav... but not enough to convince everyone.
It calls for:
Fair insights into Operating System Concepts:
Scripting/Programming: Once I was interviewing a guy for embedded tools testing and I
asked him about the languages he's comfortable with for writing test plans. His answer was English. Is that wrong, i really do not know. I am referring to one of the world's biggest semiconductor company.
On the other hand, on a training session the trainer was referring to test scripts. And later it turned out to be simple English test steps. And this happened in one of the worlds best Security Org.
Bit of everything
Everything about 1~2 things.
Do I make sense???
2. Importance of FEVIFTTWH: Almost everyone I talk to refers to usability and
usability standards. But who defines it, and what is the standardization. Who sets
them, and how do they impact.
3. Has anyone seen an application with HWTTF....., ie, the menu starting from Help,
Window, Tools and so on from the Left Hand Side. Similar happens to be with all the
Usability/GUI's and more or less goes back to what Microsoft had implemented.
4. How would you define a bug that is least severity and still remains to be priority.
Has anyone come across any product by Microsoft that displays Win instead of Windows.
Bet you will not be able to find it as for Microsoft guys this would be priority 1
5. Measuring Quality: So how do you measure Quality. The simple answer is across what
is set as a standard that the product claims to be capable of 6. QA/QC: There cannot be any other term to start with especially with respect to our
subject. Hundreds and thousands of books/jobs/references/links/tutorials/lectures etc
etc that I have come across and each one talks about QA and not about QC/software
testing. I think the industry is yet to reach such a maturity stage where these terms
get defined. QA is a non technical job (a more of a process oriented targeted for
certification, in most of the cases, although proves out to be an umbrella activity
putting Software Testing under it, which is a pure technical job.
7. White Box Testing: And all the time, it reminds me of a continent about everyone
wants to talk about as much as they possibly can. And when you are told, or try to go
there everyone runs away like a thief saving for his life. Reason is simple, Whitebox
testing is nothing but a glass box testing, where in each and every
function/unit/module/subroutine..... is tested as per the coding guidelines specified. The only thing that a tester can do here is compliance checks with respect to the coding guidelines being followed or not. Having audits, incorporating comments and so on. Also this is true mostly for larger size organizations. For very small startups or thinengineering firms, multitasking makes more sense where the developers mostly do the development as well as testing.
8. Black Box Programming: Discussed earlier
9. Unit Testing—Is it white box or black-box: Lets do a File-->New in Microsoft Word. Is it a white box or a black-box. Before integrating various modules, it would be whitebox and when it gets integrated as a product, then it would be a black box, makes sense. In case it doesn’t, please do not curse me.
10. White Box Expectations from Testers: Since the time I started by career, hardly has any interview/conference/training/event happened wherein the said subject has not
been referred to.
Friday, February 15, 2008
Building Automated Test Systems Available for Download
Abstract
Intended to benefit the Test Engineering community, the book shows how commonly available automation tools sometimes fall short of expectations.
Abhinav Vaid investigates and reports on what goes behind most of the fancy tools and to what extent they help or don’t. In this book, Abhinav deals with some popular test tools and automates a few tests. Then, the same tests are automated using free-ware tools and/or different scripting languages and technologies.
Essentially, the book is an automation project that has been implemented using 13 different programming/languages and shares technical expertise and insights to build test suites with minimal (if not zero) cost.
Building Automated Test Systems Available for Download from http://www.puretesting.com/building-automated-test-systems.html
Intended to benefit the Test Engineering community, the book shows how commonly available automation tools sometimes fall short of expectations.
Abhinav Vaid investigates and reports on what goes behind most of the fancy tools and to what extent they help or don’t. In this book, Abhinav deals with some popular test tools and automates a few tests. Then, the same tests are automated using free-ware tools and/or different scripting languages and technologies.
Essentially, the book is an automation project that has been implemented using 13 different programming/languages and shares technical expertise and insights to build test suites with minimal (if not zero) cost.
Building Automated Test Systems Available for Download from http://www.puretesting.com/building-automated-test-systems.html
Subscribe to:
Posts (Atom)