70-519 – parte 6
8:51 | Author: Unknown

Preparing For and Investigating Application Issues (15%)

 

Index

Parte 0 | Parte 1 | Parte 2 | Parte 3a | Parte 3b | Parte 4 | Parte 5

 

Choose a testing methodology

This objetive may include but is not limited to: black box, integration, regression, coverage, API testing, performance testing, security testing

 

Black Box
Black box testing. This approach tests all possible combinations of end-user actions. Black box testing assumes no knowledge of code and is intended to simulate the end-user experience. You can use sample applications to integrate and test the application block for black box testing. You can begin planning for black box testing immediately after the requirements and the functional specifications are available.
http://en.wikipedia.org/wiki/Black-box_testing

Integration 
http://en.wikipedia.org/wiki/Integration_testing
http://msdn.microsoft.com/en-us/library/aa292128(VS.71).aspx

Regression
http://en.wikipedia.org/wiki/Regression_testing
http://msdn.microsoft.com/en-us/library/aa292167(VS.71).aspx

Coverage
http://en.wikipedia.org/wiki/Code_coverage
http://msdn.microsoft.com/en-us/library/ms182496(VS.100).aspx

API testing
http://msdn.microsoft.com/en-us/library/cc300143.aspx

Performance testing
http://en.wikipedia.org/wiki/Software_performance_testing
http://msdn.microsoft.com/en-us/library/bb924375.aspx

Security testing
http://msdn.microsoft.com/en-us/magazine/cc507646.aspx


This objective does not include: load testing, Web testing, unit testing

Design an exception handling strategy

This objetive may include but is not limited to: HandleError attibute in MVC, common error pages, post-error processing, global vs page level.

HandleError attibute in MVC
The HandleError attribute (which appears on the default controllers in an MVC project) tells the framework that if an unhandled exception occurs in your controller that rather than showing the default Yellow Screen of Death it should instead serve up a view called Error. The controller-specific View folder will be checked first (eg. Views/Home/Error.aspx) and if it's not found, the Shared folder (Views/Home/Error.aspx) will be used.
http://weblogs.asp.net/scottgu/archive/2008/07/14/asp-net-mvc-preview-4-release-part-1.aspx

Common error pages
http://aspalliance.com/1008_Working_with_Custom_Error_Pages_Using_ASPNET.5

Post-error processing

Global vs. page level
http://www.15seconds.com/issue/030102.htm

    Recommend and approach to debugging


    This objetive may include but is not limited to: tools and approaches for a given scenario (for example, memory dumps, DebuggingAttributes, crashes vs hangs, deadlocks, assembly binding), when to attack a process (visual Studio Development Server vs. IIS vs. Internet Explorer), root cause analisys.

    The objetive doesn’t include: basic breakpoints

    Memory dumps

    DebuggingAttributes

    Crashes vs. hangs

    Deadlocks

    Asembly bindings

    Root cause analisys

    Recommend an approach to performace issues.

    This objetive may include but is not limited to: wich instrumentation to watch or create, (including performance counters and event tracking) to analyze performance issues, page and fragment caching.

    , |
    This entry was posted on 8:51 and is filed under , . You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.