App Verifier
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Bug Report @ OneStopTesting
Forum Discription: After Creating the Test Plan, Writing the Test Cases and using them, Finally We need to generate those Bug Reports which Proves that Testers are Good enough & most importantly Indispensable.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=571
Printed Date: 28May2024 at 3:33pm
Topic: App Verifier
Posted By: ashu
Subject: App Verifier
Date Posted: 03Apr2007 at 2:00am
Using Application Verifier Within Your Software Development Lifecycle
AppVerifier is a free download
specifically designed to detect and help debug memory corruptions,
critical security vulnerabilities, and limited user account privilege
issues. AppVerifier aids in the creation of reliable and secure
applications by monitoring an application's interaction with the
Microsoft® Windows® operating system, and profiling its use of objects,
the registry, the file system, and Win32 APIs (including heaps,
handles, and locks,). AppVerifier also includes checks to predict how
well the application will perform in non-admin environments.
When used throughout the software development lifecycle,
AppVerifier can bring cost benefits to development efforts because it
facilitates identifying problems early on when they are easier and
cheaper to fix. It also helps to detect errors that may have gone
unnoticed and ensures that the final application can be executed in
restricted (for example, non-admin) environments (this last point will
become more important with Windows Vista applications).
Problems That AppVerifier Identifies
AppVerifier helps to determine:
• When the application is using APIs correctly:
• Unsafe TerminateThread APIs.
• Correct use of Thread Local Storage (TLS) APIs.
• Correct use of virtual space manipulations (for example, VirtualAlloc, MapViewOfFile).
• Whether the application is hiding access violations using structured exception handling.
• Whether the application is attempting to use invalid handles.
• Whether there are memory corruptions or issues in the heap.
• Whether the application runs out of memory under low resources.
• Whether the correct usage of critical sections is occurring.
• Whether an application running in an administrative environment will run well in an environment with less privilege.
• Whether there are potential problems when the application is running as a limited user.
• Whether there are uninitialized variables in future function calls in a thread's context.
|
|