Canton : Valais
Durée : Temps Plein, 100%
Date de début : Tout de suite ou à convenir
Langue : Français et Anglais (Technique)
What a QA engineer does
• Write test plans from the requirements, specifications and test
• Use versioning systems to code test scripts
• Create and perform test campaign whenever it is necessary to fit in the overall planning
• Use bug tracking database to report bugs
• Analyses test results
• Reports results to the QA manager
• Raise an alert when an important issue is likely to put in jeopardy the whole project
What makes a good QA Engineer
Broad understanding of the product:
To test efficiently a product, the QA engineer must know it well enough. This
sounds obvious must unfortunately, this is often under-estimated. Knowing
well the product includes also knowing how end-users expect it to work.
Again this may sound obvious but remember that the biggest part in testing is
black-box testing. The QA engineer must have a “customer-focus” vision. But
a good QA engineer must also know how the product is designed because
the more you know the product, the better you’re able to test it. However, the
QA engineer will have to analyse the design only after his black-box testplan is
completed. Indeed, knowing the design can widely influence the test strategy.
It is better to first write the test plan with a high-level vision, then getting more
and more information to refine the testing.
Effective communication :
Communication is an extremely important skill for a QA engineer. Of course,
meetings (stand-up etc.) and status reports are part of the communication but
more importantly, a QA engineer must be particularly efficient in the following tasks:
• Direct communication with both Development and Product definition teams
• Capability to communicate with technical and non-technical people
• Having the diplomacy to say “no” when a bug is considered as not fixed
• Having the diplomacy to communicate about a bug without “offensing” the developer. Developers may often feel offensed when a bug is submited. This is 100% natural. This is why the QA engineer must have the ability to “criticize without offensing”
• Do not rely on “bug tracking” database for communication! there is nothing better that a bug tracking system to create “misunderstanding” between Development and QA teams
Testing requires a lot of creativity. Bugs are often hidden and just performing
the obvious positive tests will have only a few chances to actually find bugs.
Hence, the QA engineer must use its creativity to figure out all the scenarios
that are likely to detect a bug. In other words, the QA engineer must be able
to “see beyond the obvious”.
Quality Assurance requires knowledge about software development for two basic reasons:
• Development capabilities are required to eventually code automated tests
• If you know how to develop, you have better ideas on what is “dangerous” to code, so what to test more thoroughly
Driving for results:
A good QA engineer never forgets that the ultimate goal is not only to find bugs but also have them fixed. Once a bug has been found and has been “acknowledged” by the development team, the QA engineer may be required to “convince” people to fix it.
Following skills are essential to becoming a good software tester. Compare
your skill set against the following checklist to determine whether Software
Testing is a reality for you :
• Analytical skills: A good software tester should have sharp analytical skills. Analytical skills will help break up a complex software system into smaller units to gain a better understanding and create test cases. Not sure that you have good analytical skills
• Communication skill: A good software tester must have good verbal and written communication skill. Testing artifacts (like test cases/plans, test strategies, bug reports, etc.) created by the software tester should be easy to read and comprehend. Dealing with developers (in the event of bugs or any other issue) will require a shade of discreetness and diplomacy.
• Time Management & Organization Skills: Testing at times could be a demanding job especially during the release of code. A software tester must efficiently manage workload, have high productivity, exhibit
optimal time management, and organization skills
• GREAT Attitude: To be a good software tester you must have a GREAT attitude. An attitude to ‘test to break’, detail orientation, willingness to learn and suggest process improvements. In the software industry,
technologies evolve with an overwhelming speed, and a good software tester should upgrade his/her technical skills with the changing technologies. Your attitude must reflect a certain degree of
independence where you take ownership of the task allocated and complete it without much direct supervision.
• Passion: To Excel in any profession or job, one must have a significant degree of the passion for it. A software tester must have a passion for his / her field. BUT how do you determine whether you have a passion
for software testing if you have never tested before? Simple TRY it out and if software testing does not excite you switch to something else that holds your interest.
This list is long, so please bear with us
• Basic knowledge of Database/ SQL: Software Systems have a large amount of data in the background. This data is stored in different types of databases like Oracle, MySQL, etc. in the backend. So, there will be situations when this data needs to be validated. In that case, simple/complex SQL queries can be used to check whether proper
data is stored in the backend databases.
• Basic knowledge of Linux commands: Most of the softwareapplications like Web-Services, Databases, Application Servers are deployed on Linux machines. So it is crucial for testers to have knowledge about Linux commands.
• Knowledge and hands-on experience of a Test Management Tool: Test Management is an important aspect of Software testing. Without proper test management techniques, software testing process will fail. Test
management is nothing but managing your testing related artifacts
(tracking all the test cases written by your team, test automation tools,
• Knowledge and hands-on experience of any Defect Tracking tool- Defect Tracking and Defect life cycle are key aspects of software testing. It is extremely critical to managing defects properly and track them in a systematic manner. Defect tracking becomes necessary because the entire team should know about the defect including
managers, developers, and testers. Several tools are used to lock defects including QC, Bugzilla, Jira, etc.
• Knowledge and hands-on experience of Automation tool: If you see yourself as an “Automation tester” after a couple of years working on manual testing, then you must master a tool and get in-depth, handson knowledge of automation tools (ex. Zalenium, ).
|Job Category||Testing / Audit / Release Management|