![\"Software](\"https:\/\/blog.atinternet.com\/wp-content\/uploads\/2019\/05\/software-tester-job-definition-1024x768.jpg\")
<\/figure>\nThe software testing profession is evolving and has many facets.
\nPositions within companies are varied and job titles encompass very different
\nprofiles \u2013 analysts, designers, testers, control engineers, test engineers,
\nquality engineers, agile testers, etc. \u2013 and sometimes we all have a different
\nunderstanding of what kinds of responsibilities lie behind these designations. <\/p>\n
![\"Le](\"https:\/\/blog.atinternet.com\/wp-content\/uploads\/2019\/05\/test-logiciel-manuel.png\")
Source: https:\/\/www.qualitesoft.com<\/figcaption><\/figure>\n<\/div>\n
Most of my contacts immediately think of the repetitive nature of manual
\ntesting, due in part to the scope and variety of testing performed over the
\ncourse of development. The job of the tester is indeed often (and wrongfully)
\nassociated with boring and repetitive tasks that consist of following
\nprocedures outlined by a test manager or test lead, in order to produce a test
\nreport with an OK or KO status for each test case. The exclusively manual
\nvalidation approach, including non-regression testing, is in fact (according to
\nme \u2013 I know that opinions may differ) an outdated view of software testing,
\neven though it is still favoured by some. It is a very good model for those who
\nsell this service but has far fewer benefits for the buyer!<\/p>\n
The model presents several disadvantages:<\/p>\n
- \n
- Non-regression, by nature, signifies that as soon as the validation phase (often mistakenly called \u201crecipe\u201d) is over, and that a new version is released, you have to start over! It is therefore impossible to truly monetize your investments over the long term.<\/li>\n
- Validation timelines grow longer and longer, and this slows down deliveries. You may conclude that you need additional testers in order to speed things along, but this is a trap! <\/li>\n
- The human aspect is non-negligible: over the long term, very few people will feel fulfilled by repeating the same tasks over and over again. Meanwhile, machines do this very well, and always with a smile! <\/li>\n<\/ul>\n
These testing activities remain relevant if the need is specific, for
\nexample if you need to secure a single version of a product or assess the
\noverall quality of a project that is nearing its end. Conversely, it is difficult
\nto integrate this approach as a publisher who continually releases new features
\nwithin software systems that grow in complexity, and whose output is more and
\nmore frequent. At AT Internet, we recognize the value of manual testing, but
\nonly within a very specific context further outlined in this article
\n(acceptance). <\/p>\nThis is why I decided to write this article: to shed light on the daily
\nactivities of a \u201ctest engineer\u201d at our company and outline the rare set of
\nskills required to take on this role.<\/p>\nThe Tester Position at AT Internet<\/h2>\n
\n![\"Test](\"https:\/\/blog.atinternet.com\/wp-content\/uploads\/2019\/05\/test-automatis\u00e9.png\")
\u201cAutomated Testing\u201d
Source: https:\/\/www.qualitesoft.com<\/figcaption><\/figure>\n<\/div>\nTo understand the tester position, it is best to simply describe the
\ntester\u2019s role, as defined within our company:<\/p>\n\u201cTo contribute to the quality of the products made available to
\ncustomers, through automated validation of new features and continuous
\ndetection of regressions within existing features.\u201d<\/p>\nThe above task can be broken down into a number of activities,
\nincluding:<\/p>\n- \n
- Test design and implementation (automated, of course)<\/li>\n
- Managing tools and test environments<\/li>\n
- Reporting and following up on all detected
\nabnormalities<\/li>\n<\/ul>\n\u2026all in close collaboration with developers. Testers are also core
\nmembers of the Agile development teams.<\/p>\n\n
Independent,
\nConstructive, and Critical<\/p>\n<\/h2>\nAbove all, testers must have non-technical skills; these soft skills are
\ncrucial. <\/p>\n- \n
- They must be objective,
\nindependent thinkers<\/strong>, and have an excellent sense of customer service<\/strong>. A detected bug can never be regarded as \u201cnormal\u201d
\nif it has a truly negative impact at the customer level!<\/li>\n<\/ul>\n- \n
- Testers are also expected to communicate<\/strong> well with developers. Since they are often the bearers
\nof bad news, it is important to ensure that findings are communicated in a constructive <\/strong>manner. The end-goal is to
\nimprove the product; and never to criticize a colleague\u2019s code!<\/li>\n<\/ul>\n- \n
- While maintaining a positive attitude, testers must
\nnonetheless approach the product being tested in a critical manner<\/strong>, and most of all, never trust the code\u2014bugs are
\nalways hiding somewhere, and the trick is to find them! This is what I call the
\n\u201cprofessional pessimism\u201d <\/strong>of the
\ntrade: remaining optimistic while carefully dissecting an application in order
\nto find the problems and any other issues therein. This isn\u2019t always easy!<\/li>\n<\/ul>\nTesting Skills\u00a0\u00a0\u00a0 <\/h2>\n
In order to align with our company strategy, testers should know how to perform basic testing. Certification is available through the ISTQB Foundation<\/strong> (though it is not mandatory). The skills required allow testers to effectively analyse<\/strong> features, establish relevant testing plans<\/strong>, design<\/strong> and implement<\/strong> good test cases, and avoid common pitfalls among rookies, for example establishing tests that are dependent on one another, that ultimately verify the same thing, or that tackle too many features at once. Effective testing can be achieved using well-known techniques in the business: analysing limit values, equivalence classes, path coverage and other decision tables, for example.<\/p>\n
But that\u2019s not all\u2026<\/p>\n
I must admit that this is where things get tricky for us: our tests must
\nbe implemented by actual developers<\/strong>!
\nIn order to keep up with our continuous product integration, and considering
\nthe volume and pace of our deliveries, we have a strong need for automated
\ntesting. This is why our testers are also developers. Their skills contribute
\nto the quality of the product and serve other developers, through the
\nimplementation of efficient tools and feedback mechanisms that allow them to
\nmaintain a good sense of the quality of the code they are producing.<\/p>\nEveryone Plays a Role<\/h2>\n
![\"Processus](\"https:\/\/blog.atinternet.com\/wp-content\/uploads\/2019\/05\/proc\u00e9d\u00e9-test-logiciel-1024x392.png\")
<\/figure>\n\u201cQuality is everyone\u2019s business!\u201d said W.E. Deming. Indeed,
\neveryone has a role to play in this matter; it is not solely the domain of
\ntesters or that of an isolated team specifically dedicated to this aspect of
\nour products (in fact, we have no such team). Everyone must take part, and
\nroles and responsibilities are divided according to the testing level:<\/p>\n- \n
- Unit testing\/component integration (automated)<\/li>\n<\/ul>\n
- \n
- System testing\/integration (automated)\n
- \n
- Testers (or developers whenever necessary)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
- \n
- Acceptance testing (or \u201crecipes\u201d) (manual)\n
- \n
- Product representatives (product owners, product
\nmanagers)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\nIn some cases, our teams strategically decide to organize manual testing
\nsessions involving various employees, for example to secure the delivery of an
\napplication that was insufficiently covered by automated tests, or to deliver
\nfeatures with a high level of business risk. In these cases, an extensive ad
\nhoc recipe is needed, without implementing exceedingly complex validation systems.<\/p>\nWhy invest in automated testing?<\/h2>\n
We are committed to long-term relationships with our customers, which
\ndemand trust. We must therefore be vigilant when it comes to the quality of our
\nproducts in the medium and long term, and this involves managing technical
\ndebt, the increasing entropy of systems, and the total cost of ownership (TCO),
\nwhich testers know well.<\/p>\n
- Product representatives (product owners, product
- Acceptance testing (or \u201crecipes\u201d) (manual)\n
- Testers (or developers whenever necessary)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
- System testing\/integration (automated)\n
- Unit testing\/component integration (automated)<\/li>\n<\/ul>\n
- While maintaining a positive attitude, testers must
- Testers are also expected to communicate<\/strong> well with developers. Since they are often the bearers
- They must be objective,
![\"ROI](\"https:\/\/blog.atinternet.com\/wp-content\/uploads\/2019\/05\/roi-software-automation.png\")