-1

By reference from :

http://istqbexamcertification.com/what-is-smoke-testing-when-to-use-it-advantages-and-disadvantages-2/

Smoke testing is used in the following scenarios:

  • It is done by developers before giving build to the testing team.

  • It is done by the testers before they start the detailed testing.

Question is, can it be compromised, just because an "agile-developer" has done "Unit Testing" ?

G.S.Tomar
  • 290
  • 2
  • 14

1 Answers1

2

Ideally all testing is done by Devs:

  • This makes it clearer that introducing bad code slows down the team.
  • It also allows for more optimal automated testing as Devs can automate much better since they usually write code better.
  • It makes people in the team more cross-functional being able to do a bigger variety of work.
  • This allows team to scale horizontally better. It's harder to scale if you have people that can do a narrow type of work since this is usually a limited amount of work of that type per time unit.

Check out how Atlassian JIRA team were able to introduce Quality Assistance instead of Quality Assurance by making developers test and review better.

Unfortunately though current generation of developers is spoiled by the market demands. Today we very often have QA team which Devs can use to transfer the responsibilities for crappy work to. And this is very (very!) hard to fix unless there is a full support and understanding from the management and tech leads as well as expertise.

If you make Devs do the Smoke Testing they will quickly recognize that it's better to automate it and everyone will benefit from this. But good luck convincing them :)

Stanislav Bashkyrtsev
  • 14,470
  • 7
  • 42
  • 45
  • I agree with that answer. Just one detail: IMHO testing is perceived by many developers as 'crappy work'. It is more of an attitude then a question of generation or market demands. Have met junior and senior programmers alike who think that testing should be done by others. Unfortunately they are exactly those people who write untestable code because testing is not in the scope of their mindset. – Theo Lenndorff May 11 '17 at 08:30
  • @Stanislav Bashkyrtsev: Excellent video on "Quality Assistance instead of Quality ASsurance. Thank you – G.S.Tomar May 17 '17 at 11:29