BlackWaspTM

This web site uses cookies. By using the site you accept the cookie policy.This message is for compliance with the UK ICO law.

<< Previous | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | ... | Next >> |
Speed Test: String ConcatenationSpeed Test: String Concatenation
C# and the .NET framework provide several ways in which strings may be concatenated by appending the contents of one string to those of another. Some methods use immutable strings directly, others use mutable data to achieve faster performance.
Speed Testing and the Stopwatch ClassSpeed Testing and the Stopwatch Class
Software must operate at a speed that is acceptable to the end user. Often large improvements can be made by improving the speed of short-lived but heavily used routines. The speed of these can be accurately measured using the .NET 2.0 Stopwatch class.
Speed Test: Try / Catch BlockSpeed Test: Try / Catch Block
The try/catch block is used to capture thrown exceptions and to allow an application to recover gracefully from the problems that caused them. This article has been created to determine if the try/catch block causes a substantial performance penalty.
Speed Test: Static vs Instance MethodsSpeed Test: Static vs Instance Methods
C# allows the creation of instance members and static members. Instance members are available when an instance of the class is created and have access to the object's data. Static members do not require an object so do they increase performance?
Speed Test: Dynamic SQL vs Stored ProceduresSpeed Test: Dynamic SQL vs Stored Procedures
When developing software that uses Microsoft SQL Sever 2005 for data storage, there are various manners in which to retrieve information. Two options are dynamically-generate SQL statements and stored procedures. Does either give a performance gain?
Speed Test: Switch vs If-Else-IfSpeed Test: Switch vs If-Else-If
The .NET framework and the C# language provide two methods for conditional processing where multiple discrete values can be selected from. The switch statement is less flexible than the if-else-if ladder but is generally considered to be more efficient.
Organising NUnit TestsOrganising NUnit Tests
The fourth part of the Automated Unit Testing tutorial continues the examination of NUnit attributes. This article describes three attributes that can be used to categorise tests and determine which tests or fixtures are executed in the test runner.
Unit Testing Raised EventsUnit Testing Raised Events
Many classes use events to allow messages to be passed to other classes in a loosely coupled manner. When creating unit tests for classes that use events, the raising of those events and the arguments generated should be verified.
Unit TestingUnit Testing
This is the first in a series of articles describing the use of automated unit testing techniques. Unit testing allows verification of the functionality of a program. Automated unit testing validates software automatically by executing test code.
Creating Unit TestsCreating Unit Tests
The third part of the Automated Unit Testing tutorial examines the construction of unit tests using the NUnit testing framework. This article describes the use of the attributes that determine how the test runner executes unit test code.
<< Previous | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | ... | Next >> |