Testing

Example of preparation of Session

/// <summary>
/// Test session setting
/// Note: object Directory and Log is available.
/// </summary>
protected override void OnSessionSetting()
{
    //* register module and puts standard permissions *
    SOWIApp.Management.Module.SetModule("SOWIAppStandardFileContent", "Test",true, true,true,true,true,true,true, 0);

    //* creates a HTTP context object *
    SIC.Test.Helper.WebHost.Create();

    //* web session log in *
    SOWIWeb.Helper.Session.LogIn(Properties.Settings.Default.UserName, Properties.Settings.Default.UserPassword);

    //* puts User Role *
    SOWIApp.Management.UserRole.SetUserRole(SOWIWeb.Helper.Session.ClientID, SOWIWeb.Helper.Session.UserName);
}

Uses assembly SIC.Test.Helper for programming test units. This assembly has some helpful function e.g. supported web host for web testing.

See also Test Unit Programming

See also SIC.Test.Helper

A example of test project folders shown in Solution Explorer

Sorted by A-Z

MS Visual Studio dialog "Create Unit Tests" can't support SOWI testing because SOWI name notation has a dot character e.g. project name SIC.Draw.

Note: for test data directory and test result directory use SIC.Test.Helper.Directory and for a example see documentation "Test Unit Programming" section "Test data directory and test result directory"

SOWI Testing programming has two differ write method:

Method: SIC.Test.Helper.Print methods Write
Usage: outside of a test case but inside a test unit (the Log object isn't available)
Output: only output window

Method: this.Log method M:SIC.Test.Helper.UnitTest.Log.Write(System.String)
Usage: inside of a test case structure (the Log object is availabe)
Output: output window and protocol file

Note: methods has more variants, signature with differ parameters.

The output see into Test Output after run test (see example) and output from the Log object saves additional a protocol file in result directory.

Code example: test programming use SIC.Test.Helper.Print method Write(String).

SIC.Test.Helper.Print.Write(lTest);
SIC.Test.Helper.Print.Write("Method ButtonByAction result: " + lResult);

Test SOWI Web Helper HTML ButtonByAction on 25.04.2017 07:08:28
Method ButtonByAction result: ...

Explanation

Method LineWrite from Debug vs Console

System.Diagnostics.Debug object is the regular Output window in MS Visual Studio (see example) and this method is always available.

Test Console object is the output window of test method and this method isn't always available.

Note to Debug method WriteLine: want see output in the Debug window then run test with "Debug Tests" (context menu, short cut: Ctrl+R, Ctrl+T).

Note to SIC.Test.Helper.Print.Write: this method uses method System.Diagnostics.Debug.WriteLine

See also

• SIC.Test.HelperPrint

• SIC.Test.HelperLog all Write methods

Normally doesn't see internal class method. However! The statement: [assembly:InternalsVisibleTo("MyTests")] in ..\Properties\AssemblyInfo.cs file so can seen all methods.

[assembly: InternalsVisibleTo("easyPlanApp.Test")]

Requirement: using System.Runtime.CompilerServices;

Call from SIC.Test.Helper.WebHost method Create(String). This create a web host

/// <summary>
/// Test session setting
/// Note: object Directory and Log is available.
/// </summary>
protected override void OnSessionSetting()
{
    SIC.Test.Helper.WebHost.Create();   //* created a HTTP context object *
    //base.OnSessionSetting();          //* without session token *
}

Is Web host running then write the following output

Standard Output:    
Debugablaufverfolgung:

HTTP Request URL:      http://localhost:49292/

IIS Express running when first start project in Debug mode. Must IIS permanently running then deactivated checkbox "Enable Edit and Continue".

Context menu of IIS Express can start the site.

Reference

Other Resources