Learn the art of #QAThoughtLeadership at our professional #LinkedIngroup at:  https://www.linkedin.com/groups/QA-Thought-Leaders-3936004/about    join us now.

Several blogs, podcasts, and other forums often talk about traits and qualifications of a good software tester. One such qualification that hasn't been discussed much is the need for a tester to be a statistician.
http://www.linkedin.com/company/94462/comments?topic=5825833363763625984&type=U&scope=94462&stype=C&a=tUWY&goback=%2Ebzo_*1_*1_*1_*1_*1_*1_*1_94462

Looking forward for QA Experts
http://linkd.in/1fYPmDy

Cloud computing can be divided into two sections: the front end & the back end. Both of these ends can be connected through a network; usually, it is the internet. The front end is basically what the computer user or client sees, and the back end is the whole cloud system.
For further details, log on:-http://www.qainfotech.com/cloudtesting.html

Software quality testing, especially manual testing is all about finding and reporting bugs. Therefore, bug reports are the mirror image of the testing efforts applied. We can also say that bug reports are the most important outcome of the testing performed.
For more on this@ http://www.qainfotech.com/methodology.html

Manual software testing is the oldest type of software testing. It requires expert testers who are patient, observant, speculative, creative, innovative, open minded, resourceful, skillful and un opinionated.
For further details, log on:-http://www.qainfotech.com/manual_automation_test_experts.html

"The Error guessing is a method/technique where the experienced and good testers think of situations in which the software cannot cope with some scenarios.The experience of the tester makes him/her more successful in error guessing as he is likely to get a better understanding of the application and get to know the areas where the application might not work properly.

For example: Out of box scenarios like division by zero, or input blank or special characters for any calculations can be a situation where an application fails and tester will just do an error guessing on further stages of applications as it is more likely to fail with those scenarios.

If anyone says that "This condition/scenario is not possible" might be a good option to test that scenario.
"

Guessing Error is an art not the method of testing, Error Guessing always comes with the experience in testing. Error Guessing tests the application beyond the test cases. There are no thumb rules to define error guessing and thinking of scenarios but yes always Error Guessing will conduct on Ad-hoc basis. Usually error guessing scope rely on the software tester involved which means who uses past experience and intuition to determine what situations commonly cause software failure, or which functionality goes to break or release blocks. Error Guessing is significant in testing area is not only for testing, its also for Development. it helps us in finding out more defects from the application.

Error Guessing is not a standard testing technique and cannot be relied upon as a sure shot way of finding issues. It also depends on how much the engineer is experienced and the Know how of the application. Error guessing is simply a bluff practice and depends solely on the tester's experince and intutional capabilities, there are no rules involved. One has to guess the areas where there are chances of finiding issues. Using unusual data sets; different combinations of data; flipping between pages back and forth; performing various actions simultaneously; providing unexpected input at unexpected times are few of the techniques one uses. Error guessing should only be applied in parallel with the formal test techniues and should never be depended upon solely.

"Pros:
It is an organized and focussed way of testing.
It makes sure that everything is as per what has been documented in the requirement documents ie the Product confirms to what it is expected to perform.
It makes sure that all the basic flows of the application are covered. Cons:
Requirements are many a times not properly defined which leads to unclear tests.
In cases of requirements changes it wastes a lot of time and efforts to keep changing the tests.
It only confimrs that the system has been designed correctly.
It does not confirm in a concrete way that the output is also correct."

All software's are developed on the basis of some requirements and thus they are important while testing as well. Without requirements, what exactly do developers develop and testers would test? They would be working on assumptions, especially the testers. Without complete requirements, simply exercising on the code may reveal problems. Thus requirement based testing helps the tester to verify and validate the application. As without requirements a tester would be able to distinguish between feature and bug. There are few disadvantages of requirement based testing as well. If the requirements are not clearly defined or are misunderstood while testing, then this may result into missing some major issues.

"Pros:- Tester are aware with the requirements which helps them to identify and plan the areas which they can target. Testers can cover more type of testing as they are aware with the requirements.

Cons:- When testers are focused on requirements the chances of exploring all areas decreases which might cause problems. Poor requirement-based documents can create bigger problems and the probability of risk increases. "

Yes, for big software companies. As they spend huge amount on usability labs and they hire usability experts who are highly paid. But everyday usability projects are cheap. As Small Companies don't need any labs, they can perform in any spare space and they can trains there employee for usability testing. Thus they can save huge amount as no need to hire any professional.

For more detail, please log on to:- http://www.qainfotech.com/media_vertical.html

You need the expertise while performing security testing and tracking vulnerabilities. We at QA InfoTech have a dedicated, proficient security testing team experienced in both open source and commercial tools to take on security testing from early stages of the SDLC.

For more detail, please log on to:- http://www.qainfotech.com/security_testing_services.html

Do you think an independent software testing company is better placed if yes, why?

An Independent software testing company is the best for our software product. The main benefit is customer satisfaction in terms of quality and 24*7 work on your product in case of an offshore partner. An independent software testing company gives you the added edge with an unbiased quality analysis of your product. Organizations can benefit immensely from vast domain knowledge and testing tools expertise of their testing partners. An independent software testing company would help you achieve the "zero defect vision" by being an able partner in bug prevention instead of just doing the bug detection .This gives an edge over other software companies. Being specialized in testing, it will have the defined process and man power to ensure a timely and bug free delivery of an application. Client also prefers specialized software testing company to test their product. So, having an independent software testing company is always a good bet.

For more detail, please log on to:- http://www.qainfotech.com/knowledge_center.html

Manual software testing is one of the approaches to plan our testing as functional or automation testing has their own way of approach to plan testing. All approaches have its own way of doing it and it has own set of goal. Manual software testing uses many techniques like System testing, U.A.T Etc.
More on Manual software testing, log on to: - http://www.qainfotech.com/service_offerings.html