2 Clean up question and tagging. See https://sqa.meta.stackexchange.com/q/472/25505
source | link

When joining a new company, how does one give a test estimation effort for a piece of functionality?

When you don't have full knowledge of the system, or the functionality is brand new, wouldn't it be very hard to give a test estimation?

Could you give some examples how you've overcome this, or do you just give a rough estimate such as half the time takeit takes for the devs to code but halved?

When joining a new company how does one give a test estimation effort for a piece of functionality?

When you don't have full knowledge of the system, or the functionality is brand new wouldn't it be very hard to give a test estimation?

Could you give some examples how you've overcome this, or do you just give the time take for the devs to code but halved?

When joining a new company, how does one give a test estimation effort for a piece of functionality?

When you don't have full knowledge of the system, or the functionality is brand new, wouldn't it be very hard to give a test estimation?

Could you give some examples how you've overcome this, or do you just give a rough estimate such as half the time it takes for the devs to code?

    Bumped by Community user
1
source | link

Test estimation effort for a new piece of functionality

When joining a new company how does one give a test estimation effort for a piece of functionality?

When you don't have full knowledge of the system, or the functionality is brand new wouldn't it be very hard to give a test estimation?

Could you give some examples how you've overcome this, or do you just give the time take for the devs to code but halved?