Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/.
If we do not hit our goal we will be forced to close the site.

Current status: https://keepboardsalive.com/

Annual subs are best for most impact. If you are still undecided on going Ad Free - you can also donate using the Paypal Donate option. All contribution helps. Thank you.
https://www.boards.ie/group/1878-subscribers-forum

Private Group for paid up members of Boards.ie. Join the club.

code coverage for webapp testing

  • 26-02-2012 12:25AM
    #1
    Closed Accounts Posts: 638 ✭✭✭


    I'd like to add code coverage to automated functional and regression tests against a web app.

    In my head,I plan these steps:
    1: Instrument the byte code.
    2: deploying the code in an exploded format:
    3: run the automated web app tests.
    4: provide report of coverage

    However, Im unsure if this process would work due to the includsion of a webcontainer. Will testing the code using the front end web pages, trigger the instrumentation of the classes deployed in the unexploded deployment? Or will a web container be too high abstracted from the actual byte code to trigger the instrumentation flags?


Advertisement