Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Code Testing

Faryan Rezagholi edited this page May 1, 2019 · 1 revision

Overview

Unit and integration testing are both written in NUnit v3. Tests can be found in the mRemoteNGTests project of the main solution.

Acceptance testing is currently done manually.

Unit testing refers to testing individual components of mRemoteNG in isolation. Tests are written in such a way that only one thing is tested at a time. This usually means that one method or property of one class is tested by itself to ensure that it behaves as expected.

Integration testing seeks to verify that several components work together correctly. While components may perform correctly in isolation, bringing them together to perform a function creates more complexity that needs to be tested.

Acceptance testing is the highest level of testing performed on mRemoteNG code. During this testing, the entire application is tested through key user journeys. These user journeys are actions that a user could perform while using the program. Many times, these actions are testing multiple different subsystems of mRemoteNG.

Example:

  1. Set the option "Reconnect to previously opened sessions on startup"
  2. Open a connection
  3. Close mRemoteNG
  4. Open mRemoteNG
  5. Verify that the same connection has been opened

Clone this wiki locally