Download mbunit framework

See Trademarks for appropriate markings. Telerik Test Studio. API Reference. Initialize false ; Initialize False. For example: settings. For example: mySettings. AreEqual "Google", ActiveBrowser. ByTagIndex "title", 0. LaunchNewBrowser ' Navigate to google. InnerText End Sub. In this article. Not finding the help you need? Contact Support. Was this article helpful? Yes No. Tell us how we can improve this article. While enjoying my stay in hospital for surgery, I spent the time writing a new generative test unit framework called MbUnit.

The objective of the framework is give to the end-users the "high order" test fixtures and to the develpers the tools to build new custom fixtures without modifying the Core. To illustrate that, MbUnit implements the Simple Test Pattern and provides new fixture types, like the usefull TypeFixture which applies tests to a particular type instance.

It must emphasize that MbUnit is still a prototype, was written under the influence of morphine and other pain-killer substance, and is published on the CodeProject to get constructive feedback from CPians and specially from members of the AUT project. In the following, it is assumed that the reader has basic knownledge of unit tests NUnit, csUnit, JUnit.. In this example, we show the motivation for MbUnit and the key features about it. While developping the example, we show what kind of data-structure is needed and how the core was be built.

Let us consider the Simple Test Pattern which is implemented by most test unit framework available. This is the classic way of writing unit test as described in the figure below. A TestFixture attribute tags the test class, one SetUp method, tests are done in the Test tagged method and clean up is performed in TearDown tagged method.

This is illustrated in the left of the figure. The figure already illustrates one of the key idea of MbUnit: Fixture class should be definable at runtime by creating an execution pipe, using basic building blocks SetUpAttribute, TestAttribute, etc Test is a TestPattern. A TestFixturePattern must be able to describe itself at runtime and return it's execution path.

As mentionned in the introduction, MbUnit provides basic building blocks that a developer can use to build complex fixtures. The latter in particular has lots of usage examples, e. It doesn't really matter. Plus most sample apps that contain unit test projects tend to have tests in MSTest or NUnit or both, so it will be straightforward to run them. Then if you have any special requirements it might be worth seeing what extra features MbUnit has to offer.

If we compare the Unit Test framework, which will be the best one to start with as our applications are very small, maximum 30 to 50 pages.

Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:.