A link for 'Test Automation Guidance' to set up coded ui projects.
Sunday, July 28, 2013
.NET Framework 4.5 (Obsolete and New)
On the site of MSDN there is a list with the obsolete and new things in .NET Framework 4.5
Default comment for events
This post contains a default comment for the params for events.
A default comment is not very good, but it is easy to use it. When you can be more precise in the comment of an event you have to do this!.
/// The object that caused the event.
/// The event arguments for the event.A default comment is not very good, but it is easy to use it. When you can be more precise in the comment of an event you have to do this!.
Friday, July 5, 2013
Some tools for the solution file of a Visual Studio Solution
In the following article Tools for sln file visual studio solution file there are some utilities or useful information for the solution files of a Visual Studio solution. A must to know for each web developer!
Saturday, January 14, 2012
Testing with Visual Studio 2010
The last time I am discovering more and more the test features of Visual Studio 2010. In this blog item I discuss or mention some of these features.
It is possible to execute a code analysis after each developer build. You can enable (or disable) this in the properties of the project; see tab Code Analysis. There are several rules you can configure (globalization rules, basic correctness or of course you can customize these)
It is also possible to measure the quality of the code, with Code Metrics. Code metrics gives some overview in maintanability and complexibility. The code metrics can be used to give a progress overview in a refactor proces to the management, simply export this data to Excel. The index for maintability, complexibility, depth, code coupling and lines of code.
With the Test Impact Analysis feature Visual Studio shows you the tests which are affected on the code change. (use the Test Impace Window)
There are several tests; Code UI Test, Load Test and Web Performance test. You can also use profiling for your application. You can select CPU Samples, Instrucmentation and compare the results and find the method or class which is the most expensive.
It is possible to execute a code analysis after each developer build. You can enable (or disable) this in the properties of the project; see tab Code Analysis. There are several rules you can configure (globalization rules, basic correctness or of course you can customize these)
It is also possible to measure the quality of the code, with Code Metrics. Code metrics gives some overview in maintanability and complexibility. The code metrics can be used to give a progress overview in a refactor proces to the management, simply export this data to Excel. The index for maintability, complexibility, depth, code coupling and lines of code.
With the Test Impact Analysis feature Visual Studio shows you the tests which are affected on the code change. (use the Test Impace Window)
There are several tests; Code UI Test, Load Test and Web Performance test. You can also use profiling for your application. You can select CPU Samples, Instrucmentation and compare the results and find the method or class which is the most expensive.
Friday, January 6, 2012
Load Tests in Visual Studio
With the help of Visual Studio you can setup a Load Test. A little part of the Load Test is a Web Performance Test (prev. Web Test). A requirement for executing the test again and again without having recording it again is that the ids of the web controls are the same, between postbacks AND IIS restarts. If this is NOT the test will fail, you can solve this by making the web control id constant or maybe you can create an Extraction Rule
Monday, October 3, 2011
Lektober
Webwereld heeft de maand oktober uitgeroepen tot Lektober maand. Iedere werkdag komen lekken op websites aan de orde
- Overzicht: lektober--maand-van-het-privacylek
- lek6--escortservice-lekt-email-adressen
- lek5--sql-injectie-bij-erasmus-mc
- lek4--ziekenhuis-lekt-data-via-beterschapskaartjes
- lek3--psychologensite-loopt-leeg-door-sql-injectie
- lek2--7-gemeenten-kwetsbaar-voor-digid-lek
- lek1 blunder Logius maakt DigId fraude kinderspel
Subscribe to:
Posts (Atom)