[
[Machine Vision, Illumination] [Java, J2EE] [LabVIEW] [ORACLE] [C++] [C#] [Aspect-Oriented Programming] [Embedded] [XP Agile CI] [Software Testing] [Kanban - Agile]

Software Testing / Design Patterns

Software Testing Tools - Overview

Area Activities Tools
Standards compliance Source code audit
Coding standards compliance
Eclipse plug-ins
PMD
Metamata JavaCC
FxCop
Test coverage Code coverage
Path coverage
Requirements coverage
Rational Quantify
JStyle
Test data generation Extract data
Generate combinations
Compuware FileAid
Run-time debugging Memory leaks
Pointer errors
Rational Purify
Numega BoundsChecker
Test execution Record / playback
Results comparison
Test scripting
Unit Tests
Rational Robot
Compuware QARun, TestPartner
Mercury WinRunner/QTP
Segue SilkTest
Microsoft Application Test Center
JUnit/nUnit
Performance Testing Test response
Identify performance
bottlenecks
RadView WebLoad
Mercury LoadRunner
Compuware QARun
Borland OptimizeIT
Appperfect
Security Testing Check for compliance to Security Policy
External Penetration tests
Checks for
  1. Input Sanitization
  2. Server side validation
  3. Session state checks
  4. Discovery of further vulnerabilities -for the backdoors, debug messages, hard coded HTML comments etc.
Sleuth
Nessus
Nmap
Nikto
TamperIE
Defect Tracking Log, track and analyze defects found during testingBugzilla
TestDirector
SharePoint Portal Server
Several Client defect databases
(source) PSI

Software Testing
[ApTest Manager]
[AppLabs]
[IBM's Software Testing Best Practice
[
Ignite for Java]
[Atomic Objects, Mock Objects - Model View Presenter design pattern] [Presenter First]
[CISCO - network testing tools - reference]
[TOP 300 Freeware software: Monitoring, Spying, Security, Network]
[iTKO: LISA - codeless - WSDL/SOAP - Functional Testing tool - legacy + AJAX and SaaS ]
[SPAMfighter partnered up with Microsoft free spam intercepting tool

Testing options in Visual Studio 2008 Professional Edition

Visual Studio 2005 Team System included Microsoft testing engine (MSTest), but many developers still clamored for the testing tools to be available to a wider audience. Their efforts paid off, and MSTest is now available in Visual Studio 2008 Professional Edition.

The new Test drop-down menu within the IDE provides easy access to the testing framework. It allows you to author, generate, and run tests. Other changes have been introduced as well. For instance, a new Run Tests context-menu option has been added to the MSTest engine to simplify the execution of tests.

Test-driven development options

A basic tenet of eXtreme programming is test-driven development. The goal is to create tests before developing any code. This goes against traditional programming; instead of writing functional code and then testing code as an afterthought (if testing is performed at all), you start with the test code.

You make sure the test is correct according to the necessary logic. With the test complete, it is available when the code is ready, and you quickly know if the code performs as desired. Basically, you develop code that will pass the test.

A key part of test-driven development is the automated unit test that properly tests code functionality. Testing frameworks provide a vehicle for creating and running these tests. Various frameworks exist for .NET developers, including the following:

  • NUnit: An open source unit-testing framework for the .NET platform. It is the leader in this category, as it mimics the JUnit Java offering for the .NET platform; that is, it brings test-driven development to .NET. NUnit provides both a GUI and command-line interface. It also promotes unit testing your .NET code after coding is complete or using the test-driven approach to development. (Learn more about this framework by reading my article, “NUnit allows effective unit testing with .NET applications.)
  • xUnit.net: A freely available testing framework available via Microsoft’s version of open source with the CodePlex site. It was designed with a goal of closely aligning itself with the .NET Framework. (One of the developers of xUnit.net originally worked on NUnit.) xUnit.net was built using .NET Framework 2.0; it does not require any installation, and it offers better integration with source control tools. xUnit.net focuses heavily on test-driven development as opposed to just testing, so there are some differences with NUnit. xUnit.net is the latest to join the pool of testing frameworks.
  • MbUnit: MbUnit or the Generative Unit Test Framework for the .NET Framework is offered free of charge. It was built using the .NET Framework, and it promotes test-driven development. It offers both command-line and GUI interfaces along the lines of the same features available in NUnit.
  • QuickUnit.net: A simple testing framework written in C# for .NET applications. It is a minimalist approach to testing for developers who ignore writing unit tests and test-driven development. It can be used as a first step to become familiar with testing.
  • csUnit: A freely available testing framework that promotes test-driven development. It offers a graphical interface and easy integration with Visual Studio 2005.

Visual Studio add-ons

There are a few Visual Studio add-ons that make it easier to use the various testing frameworks within the IDE. One of the more popular products is TestDriven.NET; however, unlike the testing frameworks, it is not free. TestDriven.NET allows you to use the features of the testing framework from within Visual Studio via one click of the mouse. It works with all versions of Visual Studio.
Tony Patton
Design Patterns
...
Basel II, Borrower Risk Rating
...
The revised Basel Capital framework (Basel II) became effective for Canadian banks on November 1, 2007. Basel II is designed to more closely align regulatory capital requirements with the individual risk profile of banks by introducing substantive changes to capital requirements for credit risk and an explicit new capital charge for operational risk.

Under Basel II, there are two main methods for computing credit risk: the standardized approach, which uses prescribed risk weights; and internal ratings based approaches, which allow the use of a bank's internal models to calculate some, or all, of the key inputs into the regulatory capital calculation. The Advanced Internal Ratings Based Approach (AIRB) users are required to have sophisticated risk management systems for the calculation of credit risk regulatory capital and application of this approach could result in less regulatory capital than the use of the alternative approaches.

Once banks demonstrate full compliance with the AIRB requirements, and OSFI has approved its use, they may proceed to apply the AIRB approach in computing capital requirements. However, in order to limit sudden declines in the capital levels for the industry in aggregate, capital floors were introduced for the first two years after full implementation of AIRB. A capital floor of 90% of the Basel I calculation will apply in the first year of full approval and 80% in the second year, if required. SEC Info: Bank of Nova Scotia
Market share




Feedback:


Integration Notes

[Machine Vision, Illumination] [Java, J2EE] [LabVIEW] [ORACLE] [C++] [C#] [Aspect-Oriented Programming] [Embedded] [XP Agile CI] [Kanban - Agile]

[ CAN 2.0 (Bosch basic specification) ]

PhotoImpact
-->