Too many UI changes - Descriptive is best for maintenance

On Fri, Jan 10, 2014 at 7:10 AM, george <[email protected]> wrote:

>
> Our application is very dynamic. Not a lot is changing during new
> iterations and releases, however its very data driven.
> There are lots of modules and functionality that we need to retest during
> new builds. There are only 3 of us, having NO time to do suficienlt end to
> end testing.I want to build some smoke testsing scripts to use during quick
> regression and not waist to much time.
>
> I am debating whether or not to do only descriptive programing or have
> object repository going (or Both in this case).
>
> What approach should I take?
> Which would require less maintenance in the future.
>
> thanks.
>
>
>  --
> --
> You received this message because you are subscribed to the Google
> "QTP - HP Quick Test Professional - Automated Software Testing"
> group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/MercuryQTP?hl=en
>
> ---
> You received this message because you are subscribed to the Google Groups
> "QTP - HP Quick Test Professional - Automated Software Testing" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>

-- 
-- 
You received this message because you are subscribed to the Google
"QTP - HP Quick Test Professional - Automated Software Testing"
group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/MercuryQTP?hl=en

--- 
You received this message because you are subscribed to the Google Groups "QTP 
- HP Quick Test Professional - Automated Software Testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to