Interested to Buy Any Domain ? << Click Here >> for more details...
Answer Posted / vasu
1.Test to Break: This attitude is very important for a
tester, Test to Break attitude can be developed by negative
thinking that a application break, hyper sensitivity towards
smallest of small details regarding requirement.
2.Good observer: Tester should be having an attitude of
paying attention even to the minutest details. For e.g.
Sentence related to copyright act is missing or copyright
symbol is missing will be creating a huge impact to web
application when in live.
3. Positive attitude: Positive attitude for find issues
and bugs is important of a tester.
4. Requirement understanding: Tester should have the
capability of understand the customers and end user’s point
of view.
5.Diplomacy: Tester should be diplomatic while
communicating an bug or an issue to developer. Bug or issue
should be communicated to developer in such a way that it
does not hurt their ego and should not be offensive because
of fact that even they lot of their hard work to develop an
application and tester tell its not proper.
6.Communication: Tester should have good and effective
communication to different sections of people technical
(developers) and non-technical (customers) and ability to
understand various sides of an issue.
7.Judgment skills: Judgment skills are needed to assess
high-risk areas of an application on which to focus testing
efforts when time is limited.
8. Ability to find problems: An ability of to find
problem is also one of the important skills which can be
developed by paying attention to details and comparing with
requirements.
9.Software development life cycle knowledge: Knowledge
about entire software development process and how it can fit
into the business approach and goals of the organization.
10.Tolerance to chaos: Testers have to be flexible and
be able to drop things when blocked and move on to another
thing that’s not blocked. Testers always have many
(unfinished) irons in the fire. In this respect, good
testers differ from programmers. A compulsive need to
achieve closure is not a bad attribute in a
programmer-certainly serves them well in debugging-in
testing, it means nothing gets finished. The testers’ world
is inherently more chaotic than the programmers’.
11.Honesty: Testers are fundamentally honest and
incorruptible. They’ll compromise if they have to, but
they’ll righteously agonize over it. This fundamental
honesty extends to a brutally realistic understanding of
their own limitations as a human being. They accept the idea
that they are no better and no worse, and therefore no less
error-prone than their programming counterparts. So they
apply the same kind of self-assessment procedures that good
programmers will. They’ll do test inspections just like
programmers do code inspections. The greatest possible crime
in a tester’s eye is to fake test results.
| Is This Answer Correct ? | 6 Yes | 0 No |
Post New Answer View All Answers
how much it is necessary that if u r a sqa engineer then ur programming should be strong or either u have only concepts of it but u r not a good programmer.If the person is not a good programmer then do they are able to make their carrer in this field of qa and do it has good scope for them being not a good programmer?
What is extreme programming and what is it got to do with testing?
Is automating some test case is important? What about the maintenance? When will automated test become uneffective?
Field level test cases are developed using AF TOD to validate individual fields on a screen using a black box testing methodology. IN THIS CONTEXT WHAT IS "AF TOD"
What is a test strategy and what does it include?
What are the common problems with software automation?
What type of tests you perform on the web based application?
What is process area in cmmi?
What the first thing You’ll do as a SQA Tester if I hired You?
Tell me some key points to consider while writing a bug report.
What is the difference in responsibilities of programmers and qa analyst?
What should Development require of QA?
Diffrence b/w compiled module and shared repository?
What are the things the tests ensure?
What are the automation challenges that sqa(software quality assurance) team faces while testing?
