
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
ts-test-decorators
Advanced tools
Write your tests in a Java-like annotation-driven manner via JS decorators.
This project will help to smoothly migrate from Java to Javascript automation.
Let's say we have the following test written in Java:
public class AuthorizationTests {
@Issue("42")
@TmsLink("58")
@Feature("Login")
@Story("58")
@Severity(SeverityLevel.BLOCKER)
@Test(dataProvider = "testData")
public void userShouldBeAbleToSignIn(User user) {
open(LoginPage.class)
.loginWith(user)
.select(ProfilePage.class);
verifyThat(at(ProfilePage.class))
.fullNameIs(user.getFullName())
.usernameIs(user.getUsername());
}
@DataSupplier
public StreamEx testData() {
return StreamEx.of(
new User('stranger', '123456', 'Strange Person'),
new User('test', '123456', 'Test User')
);
}
}
Everyone in a Java world get used to strict types, classes and annotations. You may wonder how to achieve the same in JS?
The answer is using Typescript and decorators.
@testdeck/mocha will help us with core features. However, it has nothing to do with Allure. Moreover, there's no flexible DataProvider mechanism available.
This library fills these gaps, so that you can write your tests the following way:
import { Severity } from "allure2-js-commons"
import { suite, test } from '@testdeck/mocha'
import {
assignPmsUrl,
assignTmsUrl,
decorate,
data,
description,
feature,
issue,
owner,
severity,
story,
tag,
testCaseId
} from 'ts-test-decorators'
import { allure, MochaAllure } from 'allure-mocha/runtime'
@suite
class AuthorizationTests {
static testData = () => {
return new User('Test', 'User')
}
before() {
const gitHubUrl: string = 'https://github.com/sskorol/ts-test-decorators/issues'
assignPmsUrl(gitHubUrl)
assignTmsUrl(gitHubUrl)
decorate<MochaAllure>(allure)
}
@issue('42')
@testCaseId('58')
@severity(Severity.BLOCKER)
@feature('Login')
@story('58')
@owner('skorol')
@tag('smoke')
@description('Basic authorization test.')
@data(AuthorizationTests.testData)
@data.naming((user: User) => `${user} should be able to sign`)
@test
userShouldBeAbleToSignIn(user: User) {
open(LoginPage)
.loginWith(user)
.select(ProfilePage)
verifyThat(atProfilePage)
.fullNameIs(user.fullName)
.usernameIs(user.username)
}
}
npm i ts-test-decorators --save-dev
or via yarn:
yarn add ts-test-decorators --dev
As it's an extension to allure-js and testdeck, you have to install the following dependencies:
Either add allure-mocha into .mocharc.json:
{
"require": "source-map-support/register",
"reporter": "allure-mocha"
}
Or pass the same value via commandline / scripts:
mocha -R allure-mocha
tsconfig.json may look like the following:
{
"compilerOptions": {
"target": "es2017",
"module": "commonjs",
"inlineSourceMap": true,
"inlineSources": true,
"emitDecoratorMetadata": true,
"experimentalDecorators": true,
"declaration": true,
"lib": [
"es7"
],
"types": [
"node",
"mocha",
"chai"
],
"removeComments": true,
"noImplicitAny": false,
"baseUrl": ".",
"paths": {
"*": [ "./*" ],
"src/*": ["./src/*"]
},
"typeRoots": [
"node_modules/@types"
]
},
"include": [
"./src/**/*.ts"
],
"exclude": [
"node_modules"
]
}
Now you can use the following decorators:
attachment<T>(name: string, type: ContentType)
issue<T>(idFn: string | ((arg: T) => string))
testCaseId<T>(idFn: string | ((arg: T) => string))
feature<T>(featureFn: string | ((arg: T) => string))
story<T>(storyFn: string | ((arg: T) => string))
severity<T>(severityFn: Severity | string | ((arg: T) => string | Severity))
tag<T>(tagFn: string | ((arg: T) => string))
owner<T>(ownerFn: string | ((arg: T) => string))
epic<T>(epicFn: string | ((arg: T) => string))
description<T>(descriptionFn: string | ((arg: T) => string))
step<T>(nameFn: string | ((arg: T) => string))
data(params: any, name?: string)
data.naming(nameForTests: (parameters: any) => string)
To activate decorators you have to provide Allure implementation in runtime. You can do that the following way:
import { decorate } from 'ts-test-decorators';
import { allure, MochaAllure } from 'allure-mocha/runtime'
// ...
before() {
decorate<MochaAllure>(allure)
}
If you want to set you own trackers' URLs, do the following:
import { assignPmsUrl, assignTmsUrl } from 'ts-test-decorators';
// ...
before() {
const gitHubUrl: string = 'https://github.com/sskorol/ts-test-decorators/issues'
assignPmsUrl(gitHubUrl)
assignTmsUrl(gitHubUrl)
}
@data is not related to Allure. It's just a wrapper for testdeck @params decorator.
Also, be aware of @test and @data order. They should be always put before actual test method signature.
See mocha-allure2-example project, which is already configured to use latest Allure 2 features with decorators support.
@srg-kostyrko for help and assistance.
FAQs
Write your tests in a Java-like annotation-driven manner via JS decorators.
We found that ts-test-decorators demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.