Skip to main content
Software Quality Assurance & Testing

Return to Question

edited body
Source Link
LeBrequin
LeBrequin
  • 437
  • 2
  • 7
  • 16

I don't know if you have faced the situation but I wanted to open a discussion about the following topic: How to motive developers to test their own work?

When I mean "their own work" it can go from a feature they have realized or a fix to a bug.

I'm the only QA in a team of 9 developers for a project involving mobile, web and server work. The amount of work is more and more important and my time becomes precious. The current problem that I sometimes experience is that some developers develop features or fixes but don't really test what they have done. They compile and then send that to me for testing.

With my productproject manager who is also a developer we want to incite other developers to review their own work and perform a minimum of testing. It is annoying to see that a bug is still happening with exactly the same reproduction steps when i'm reviewing a fix.

How is it working in your team? Did you faced this issue also? I know that Atlasssian is doing a great job on this side and motivate developers to review and test their jobs.

I don't know if you have faced the situation but I wanted to open a discussion about the following topic: How to motive developers to test their own work?

When I mean "their own work" it can go from a feature they have realized or a fix to a bug.

I'm the only QA in a team of 9 developers for a project involving mobile, web and server work. The amount of work is more and more important and my time becomes precious. The current problem that I sometimes experience is that some developers develop features or fixes but don't really test what they have done. They compile and then send that to me for testing.

With my product manager who is also a developer we want to incite other developers to review their own work and perform a minimum of testing. It is annoying to see that a bug is still happening with exactly the same reproduction steps when i'm reviewing a fix.

How is it working in your team? Did you faced this issue also? I know that Atlasssian is doing a great job on this side and motivate developers to review and test their jobs.

I don't know if you have faced the situation but I wanted to open a discussion about the following topic: How to motive developers to test their own work?

When I mean "their own work" it can go from a feature they have realized or a fix to a bug.

I'm the only QA in a team of 9 developers for a project involving mobile, web and server work. The amount of work is more and more important and my time becomes precious. The current problem that I sometimes experience is that some developers develop features or fixes but don't really test what they have done. They compile and then send that to me for testing.

With my project manager who is also a developer we want to incite other developers to review their own work and perform a minimum of testing. It is annoying to see that a bug is still happening with exactly the same reproduction steps when i'm reviewing a fix.

How is it working in your team? Did you faced this issue also? I know that Atlasssian is doing a great job on this side and motivate developers to review and test their jobs.

Tweeted twitter.com/StackSQA/status/928565314174046209
Source Link
LeBrequin
LeBrequin
  • 437
  • 2
  • 7
  • 16

How to motivate devs to test their own work?

I don't know if you have faced the situation but I wanted to open a discussion about the following topic: How to motive developers to test their own work?

When I mean "their own work" it can go from a feature they have realized or a fix to a bug.

I'm the only QA in a team of 9 developers for a project involving mobile, web and server work. The amount of work is more and more important and my time becomes precious. The current problem that I sometimes experience is that some developers develop features or fixes but don't really test what they have done. They compile and then send that to me for testing.

With my product manager who is also a developer we want to incite other developers to review their own work and perform a minimum of testing. It is annoying to see that a bug is still happening with exactly the same reproduction steps when i'm reviewing a fix.

How is it working in your team? Did you faced this issue also? I know that Atlasssian is doing a great job on this side and motivate developers to review and test their jobs.