When we are writing the programming language code, it is crucial to plan to tackle any errors that may occur while the application is running. Though an application may perform perfectly when it is used by a developer in a particular development environment, there exist innumerable errors that can crop up in an application after it is deployed. There is no way to calculate that how a user may effort to exploit an application once an application is deployed and what other applications are installed on the client machine this factors can influence the performance of application.Thus, most programming languages incorporate facilities for handling errors. Errors also occur when an application is not independent that is, if it is dependent on something which is being provided or controlled externally. That is why it is necessary to placed Error handling code at points where an error can possibly occur.
Testing and debugging code written in a Silverlight application is quite simple and can occur in one of 2 given scenarios’:
In 1st scenario- Silverlight application executes only on the client where as,
In 2nd scenario- Silverlight application makes calls to a Web service.
Prior modules have enclosed thoroughly that how to setup and then configure the environment for testing a Silverlight application that uses Visual Studio 2008 for calling a Web service.The Visual Studio 2008 debugger is one of the leading and amazingly powerful, and includes additional features than most developers will make use of it ever. The most useful and simplest feature of the Visual Studio 2008 debugger is the capability to set breakpoints in code. When a breakpoint is set in the code and execution of code come across the breakpoint, execution halts at that particular point and each facet of code execution can be scrutinized or analyze in detail. In
An application undergoes various levels and rounds of testing before being handed over to users in a production environment. Actually, an application security should be taken into account as early as possible and a proper security plan must be created at some point in the planning phase. The testing plan should document the levels of testing that will be performed on an application and also who will be performing the testing. The different levels of testing incorporate:
1) Unit testing- is a technique by which different units of source code are deployed for testing to find out whether they are fit for use or not.
2) Regression testing- is any kind of software testing that search for to exposing new errors, in existing functionality after modification have been made in the software.
3) Load testing - is the method of laying demand on a device or a system and then measuring its response. It is performed to verify the behavior of the system under both normal s well as expected peak load conditions.
4) Integration testing- is software testing in which separate software modules are mingled and tested whole as a group.