What are qualities of good software tester?

Answer 1

Individual Characteristics:

Communication skills - having the capacity to discover issues doesn't make a difference if the analyzer can't convey them precisely and carefully.

Support - This is something of a subset of interchanges, yet merits its own posting in light of the fact that an extraordinary analyzer has the capacity give strong, explored reasons why particular issues should be altered; ready to advocate for testing all in all and their group in particular.

Scrupulousness - this may be a bit threadbare, however having the capacity to notice that some seemingly insignificant detail is off is significant to discovering issues - also approving complex business rationale.

Enormous picture thinking - It's a test to have the capacity to concentrate on little subtle elements and huge picture in the meantime, yet awesome analyzers can and do. Following a little detail without losing the 10,000 foot view is vital.

Perseverance - when something baffling and irregular is occurring, an extraordinary analyzer continues attempting distinctive thoughts to pursue down the main driver.

Quick learner - I've yet to work in a domain where the expectation to absorb information wasn't so steep it could be portrayed as a learning bluff. With shade.

Specialized Skills:

Nature with programming and equipment - This doesn't mean in-your-face nerd, yet knowing the contrast between a serial and a parallel port matters if the application being tried uses both.

Fundamental to direct learning of SQL - having the capacity to discover data in a database is priceless to each testing occupation I've expected to do. Having the capacity to control database data is additionally useful.

Speaker to Management - having the capacity to make an interpretation of from developer to ordinary human or to director is especially imperative if the test gathering doesn't have a lead or administrator doing this occupation for them. Every one of the three gatherings will utilize the same words however mean very distinctive things by them.

Perused code - having the capacity to peruse code is really more vital than having the capacity to compose code, in my experience. It permits the analyzer to follow rationale and discover potential edges to the application.

Limit Rider - looking for limits in the application and practicing them means pushing the application in the spots where it's destined to have shortcomings.