Results 1 to 4 of 4
  1. #1

    Testing OCX controls

    User Andrew Wong (Andrew.Wong@bedbath.com.nospam) posted:

    Hi All,

    Once a OCX control is tested. Does it need to be tested again if your
    using it in a new application? Or just test to see it integrated properly
    with the new app.
    Any Software Tester thoughts on this subject would be greatly appreciated.

    Penny for Your Thoughts



  2. #2

    Re: Testing OCX controls

    User PHIL BEVAN (PHIL.BEVAN@thales-cs.com.nospam) posted:

    You test it with the application, no telling how it could interact so you
    don't ignore it.

    You do have a suite of basic OCX tests that you can do for the app haven't
    you? Then

  3. #3

    Re: Testing OCX controls

    User DAVID MARSH (DAVID.MARSH@thales-cs.com.nospam) posted:

    If you base your testing on the documentation for specifications and
    requirements then you don't need opinions.

    For example if you have tested something then if it is used in another
    application if the pecs and requirements give you a list of stuff to test
    then the something will either get tested as part of those tests, or you
    will find your documentation lacking because there is no reason to have the
    something there. After all it is not just the item itself that would get
    tested but also any interfaces.

    And if you have some automation functions for the control already then no
    worries, 5 minute job.

  4. #4

    Re: Testing OCX controls

    User Andrew Wong (Andrew.Wong@bedbath.com.nospam) posted:


    Thank you for your input. Yes, it is in the tech spec and yes it will be
    part of the test.





Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
BetaSoft Inc.
All times are GMT -8. The time now is 05:51 PM.

Copyright BetaSoft Inc.