DRAMA 0.3.17
See the version list below for details.
dotnet add package DRAMA --version 0.3.17
NuGet\Install-Package DRAMA -Version 0.3.17
<PackageReference Include="DRAMA" Version="0.3.17" />
paket add DRAMA --version 0.3.17
#r "nuget: DRAMA, 0.3.17"
// Install DRAMA as a Cake Addin #addin nuget:?package=DRAMA&version=0.3.17 // Install DRAMA as a Cake Tool #tool nuget:?package=DRAMA&version=0.3.17
DRAMA
6th Generation Enterprise-Grade .NET-Based Test Automation Framework
</br>
FAQ
Q: Where to download Playwright images from, for my solution which integrates DRAMA?
A: The Docker image tag lists can be found at the following locations:
Ubuntu:
https://mcr.microsoft.com/v2/playwright/tags/list
Ubuntu With .NET:
https://mcr.microsoft.com/v2/playwright/dotnet/tags/list
</br>
Q: How do I run my tests in a CI/CD pipeline?
A: Either use a PowerShell script or a Bash script, along the lines of the examples below:
# set the environment variable for the results path, which DRAMA will look for at runtime
[Environment]::SetEnvironmentVariable("DRAMA_RESULTS_PATH", $PSScriptRoot)
${RESULTS_PATH} = [Environment]::GetEnvironmentVariable("DRAMA_RESULTS_PATH")
Write-Host "[DEBUG] DRAMA Results Path: ${RESULTS_PATH}" -ForegroundColor Yellow
# set the environment variable for the test run name, which DRAMA will look for at runtime
[Environment]::SetEnvironmentVariable("DRAMA_TEST_RUN_NAME", (Get-Date -Format "yyyy-MM-dd_HH-mm-ss"))
${TEST_RUN_NAME} = [Environment]::GetEnvironmentVariable("DRAMA_TEST_RUN_NAME")
Write-Host "[DEBUG] DRAMA Test Run Name: ${TEST_RUN_NAME}" -ForegroundColor Yellow
# create a variable that points to the directory where the test run results will be stored
# this directory needs to be known prior to DRAMA runtime, so that it can be passed to the "dotnet test" command
# both DRAMA and MSTest artefacts will be generated at this path
${TEST_RUN_RESULTS_PATH} = [IO.Path]::Combine("${RESULTS_PATH}", "DRAMA_RESULTS", "${TEST_RUN_NAME}")
Write-Host "[DEBUG] DRAMA Test Run Results Path: ${TEST_RUN_RESULTS_PATH}" -ForegroundColor Yellow
# start the DRAMA test run
dotnet test `
--filter "TestCategory!=DEBUG&TestCategory!=DEMO" `
--logger "console;verbosity=detailed" `
--logger "trx;LogFileName=${TEST_RUN_NAME}.trx" `
--logger "html;LogFileName=${TEST_RUN_NAME}.html" `
--logger "junit;LogFileName=${DRAMA_TEST_RUN_NAME}.junit" `
--results-directory "${TEST_RUN_RESULTS_PATH}"
# set the environment variable for the results path, which DRAMA will look for at runtime
export DRAMA_RESULTS_PATH=${PWD}
echo "[DEBUG] DRAMA Results Path: ${DRAMA_RESULTS_PATH}"
# set the environment variable for the test run name, which DRAMA will look for at runtime
export DRAMA_TEST_RUN_NAME=$(date "+%Y-%m-%d_%H-%M-%S")
echo "[DEBUG] DRAMA Test Run Name: ${DRAMA_TEST_RUN_NAME}"
# create a variable that points to the directory where the test run results will be stored
# this directory needs to be known prior to DRAMA runtime, so that it can be passed to the "dotnet test" command
# both DRAMA and MSTest artefacts will be generated at this path
export TEST_RUN_RESULTS_PATH="${DRAMA_RESULTS_PATH}/DRAMA_RESULTS/${DRAMA_TEST_RUN_NAME}"
echo "[DEBUG] DRAMA Test Run Results Path: ${TEST_RUN_RESULTS_PATH}"
# start the DRAMA test run
dotnet test \
--filter "TestCategory!=DEBUG&TestCategory!=DEMO" \
--logger "console;verbosity=detailed" \
--logger "trx;LogFileName=${DRAMA_TEST_RUN_NAME}.trx" \
--logger "html;LogFileName=${DRAMA_TEST_RUN_NAME}.html" \
--logger "junit;LogFileName=${DRAMA_TEST_RUN_NAME}.junit" \
--results-directory "${TEST_RUN_RESULTS_PATH}"
</br>
Q: How do I write a Docker file, for my solution which integrates DRAMA?
A: Create a file called DOCKERFILE
, which will contain the image definition. Also create a file called .DOCKERIGNORE
, which will be identical to the .GITIGNORE
file, except for the addition of excluding Git files, more specifically the .git
directory. Assuming a test automation solution called CSyphus, an example Docker file looks like the following:
#################################################################################################### STAGE 1
# add the Playwright base image, based on Ubuntu 20.04 LTS (Focal Fossa), optionally with .NET
# https://mcr.microsoft.com/v2/playwright/tags/list
# https://mcr.microsoft.com/v2/playwright/dotnet/tags/list
FROM mcr.microsoft.com/playwright:v1.30.0-focal AS dependency-resolver
# https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
RUN curl -sSL https://dot.net/v1/dotnet-install.sh | bash /dev/stdin --version 7.0.102
# add "dotnet" to the system path
# https://github.com/dotnet/sdk/issues/9911
RUN export PATH="$PATH:$HOME/.dotnet"
# disable .NET CLI Tools telemetry
# https://aka.ms/dotnet-cli-telemetry
ENV DOTNET_CLI_TELEMETRY_OPTOUT true
# display .NET information
RUN dotnet --info
#################################################################################################### STAGE 2
# start second stage after all dependencies have been resolved
FROM dependency-resolver AS solution-file-handler
# set the working directory
WORKDIR /CSyphus
# copy the solution files to the working directory
COPY . .
#################################################################################################### STAGE 3
# start third stage after all solution files are in place
FROM solution-file-handler
# restore NuGet packages
RUN dotnet restore
# clean solution, if this is needed
RUN dotnet clean
# build solution
RUN dotnet build
# create persistent volume for accessing the test results
VOLUME /DRAMA_RESULTS
# # # set the test run profile
#
# ENV DRAMA_PROFILE "CI/CD Pipeline"
#
# for running the automated tests against more than one environment
# this variable needs to be set by passing it as a parameter to the `docker run` command
# when starting the test run via the build pipeline
# instead of setting it directly in this docker file
#
# e.g.: docker run -e DRAMA_PROFILE="CI/CD Pipeline" --name CSyphus -v "$PWD/test-artefacts":"/CSyphus/DRAMA_RESULTS" testware/csyphus:latest
# set container entry point and overridable parameters
CMD ["bash", "csyphus.sh"]
</br>
Q: How do I set up my solution which integrates DRAMA to run via a GitLab pipeline?
A: Create a .GITLAB-CI.YML
configuration file along the lines of the following:
stages:
- execute
# https://mcr.microsoft.com/v2/playwright/tags/list
# https://mcr.microsoft.com/v2/playwright/dotnet/tags/list
image: mcr.microsoft.com/playwright:v1.30.0-focal
run-tests:
stage: execute
rules:
- if: $CI_COMMIT_BRANCH == "main" && $CI_PIPELINE_SOURCE != "push"
tags:
- SONIC # explicitly specify runner by name
script:
- curl -sSL https://dot.net/v1/dotnet-install.sh | bash /dev/stdin --version 7.0.102 # https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-install-script
- export PATH="$PATH:$HOME/.dotnet" # https://github.com/dotnet/sdk/issues/9911
- export DOTNET_CLI_TELEMETRY_OPTOUT=true # https://aka.ms/dotnet-cli-telemetry
- dotnet --info
- dotnet build
- DRAMA_RESULTS_PATH=${PWD}
- |
echo "[DEBUG] DRAMA Results Path: ${DRAMA_RESULTS_PATH}"
- DRAMA_TEST_RUN_NAME=$(date "+%Y-%m-%d_%H-%M-%S")
- |
echo "[DEBUG] DRAMA Test Run Name: ${DRAMA_TEST_RUN_NAME}"
- TEST_RUN_RESULTS_PATH="${DRAMA_RESULTS_PATH}/DRAMA_RESULTS/${DRAMA_TEST_RUN_NAME}"
- |
echo "[DEBUG] DRAMA Test Run Results Path: ${TEST_RUN_RESULTS_PATH}"
- EXIT_CODE=0
- >
dotnet test
--filter "TestCategory!=DEBUG&TestCategory!=DEMO"
--logger "trx;LogFileName=${DRAMA_TEST_RUN_NAME}.trx"
--logger "html;LogFileName=${DRAMA_TEST_RUN_NAME}.html"
--logger "junit;LogFileName=${DRAMA_TEST_RUN_NAME}.junit"
--results-directory "${TEST_RUN_RESULTS_PATH}"
|| EXIT_CODE=$?
- |
echo "[DEBUG] DRAMA Test Run Exit Code: ${EXIT_CODE}"
- OUTPUT_TEST_RESULTS="${PWD}/RESULTS"
- if [ -d "${OUTPUT_TEST_RESULTS}" ]; then rm -rf "${OUTPUT_TEST_RESULTS}"; fi
- LATEST_RESULTS="$(ls -td ${PWD}/DRAMA_RESULTS/* | head -1)"
- |
echo "[DEBUG] Latest Set Of Test Results: ${LATEST_RESULTS}"
- mv "${LATEST_RESULTS}" "${OUTPUT_TEST_RESULTS}"
- rm -rf "${PWD}/DRAMA_RESULTS"
- exit $EXIT_CODE
variables:
DOTNET_CLI_TELEMETRY_OPTOUT: "true"
artifacts:
name: RESULTS
when: always
paths:
- ./RESULTS/*.*
reports:
junit:
- ./RESULTS/*.junit
</br>
Q: How to install Playwright locally, for development purposes?
A: Follow the steps below:
- install PowerShell by executing
dotnet tool install --global PowerShell
- build the solution and navigate to the directory which contains both
playwright.ps1
andMicrosoft.Playwright.dll
(e.g..\bin\Debug\net7.0
) - open a PowerShell terminal and execute
pwsh playwright.ps1 install
</br>
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net7.0
- ExtentReports (>= 4.1.0)
- JunitXml.TestLogger (>= 3.0.124)
- Microsoft.Data.Sqlite (>= 7.0.2)
- Microsoft.Playwright (>= 1.30.0)
- MySql.Data (>= 8.0.32)
- Newtonsoft.Json.Schema (>= 3.0.14)
- Npgsql (>= 7.0.1)
- NUnit (>= 3.13.3)
- Oracle.ManagedDataAccess.Core (>= 3.21.90)
- SpecFlow (>= 3.9.74)
- System.Data.SqlClient (>= 4.8.5)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.0.14 | 216 | 12/31/2023 |
1.0.12 | 167 | 11/29/2023 |
1.0.11 | 129 | 11/28/2023 |
1.0.10 | 149 | 11/24/2023 |
0.3.22 | 492 | 5/15/2023 |
0.3.21 | 245 | 4/28/2023 |
0.3.20 | 184 | 4/25/2023 |
0.3.19 | 217 | 4/12/2023 |
0.3.18 | 346 | 3/10/2023 |
0.3.17 | 313 | 2/14/2023 |
0.3.16 | 340 | 12/20/2022 |
0.3.15 | 378 | 11/28/2022 |
0.3.14 | 327 | 11/22/2022 |
0.3.13 | 375 | 11/14/2022 |
0.3.12 | 572 | 6/24/2022 |
0.3.11 | 683 | 3/8/2022 |
0.3.7 | 648 | 2/24/2022 |
0.2.6 | 590 | 2/9/2022 |
0.2.5 | 644 | 1/24/2022 |
0.2.4 | 598 | 1/24/2022 |
0.2.3 | 592 | 1/20/2022 |
0.2.2 | 595 | 1/20/2022 |
0.2.1 | 596 | 1/18/2022 |
0.2.0 | 469 | 1/11/2022 |
0.1.3 | 4,547 | 11/24/2021 |
0.1.2 | 342 | 11/16/2021 |
0.1.1 | 474 | 11/3/2021 |
0.1.0 | 459 | 10/20/2021 |
Death Is Just One Character I Play, My Real Name Is Change