test-data-supplier | TestNG DataProvider on steroids | Automation library

by sskorol Java Version: 2.3.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | test-data-supplier Summary

test-data-supplier is a Java library typically used in Automation, Selenium applications. test-data-supplier has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. However test-data-supplier build file is not available. You can download it from GitHub, Maven.

This repository contains TestNG DataProvider wrapper (latest version is based on TestNG 7.4.0) which helps to supply test data in a more flexible way.

Support

Quality

Security

License

Reuse

Support

test-data-supplier has a low active ecosystem.

It has 136 star(s) with 22 fork(s). There are 13 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 68 have been closed. On average issues are closed in 8 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of test-data-supplier is 2.3.0

Quality

test-data-supplier has 0 bugs and 0 code smells.

Security

test-data-supplier has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

test-data-supplier code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

test-data-supplier is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

test-data-supplier releases are available to install and integrate.

Deployable package is available in Maven.

test-data-supplier has no build file. You will be need to create the build yourself to build the component from source.

Installation instructions are not available. Examples and code snippets are available.

test-data-supplier saves you 909 person hours of effort in developing the same functionality from scratch.

It has 2076 lines of code, 265 functions and 64 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed test-data-supplier and discovered the below as its top functions. This is intended to give you an instant insight into test-data-supplier implemented functionality, and help decide if they suit your requirements.

Post transformation call .
Get the metadata of the factory method .
Transforms the result set .
Returns a stream of entities .
Gets data supplier method .
Returns list of indices .
Invoked when data provider is ready .
Load implementations of the given type .
Provides an Iterator for sequence data
Provide data provider for parallel test execution .

Get all kandi verified functions for this library.

test-data-supplier Key Features

No Key Features are available at this moment for test-data-supplier.

test-data-supplier Examples and Code Snippets

No Code Snippets are available at this moment for test-data-supplier.

Community Discussions

Trending Discussions on test-data-supplier

TestNG tests execution against JDK 9 module causes InaccessibleObjectException

QUESTION

TestNG tests execution against JDK 9 module causes InaccessibleObjectException

Asked 2017-Dec-01 at 12:05

I'm trying to transform the following library into Java 9 module: https://github.com/sskorol/test-data-supplier

Followed this guide: https://guides.gradle.org/building-java-9-modules

After some manipulations and refactoring (couldn't manage lombok issues, so just temporary removed it), I have the following module-info.java:

...

ANSWER

Answered 2017-Dec-01 at 12:05

Have an assumption that the root cause in a TestNG reflection usage within ObjectFactoryImpl against test classes.

It's one of two causes, yes. The other is that, apparently, Gradle runs your tests as a module. As you point out, there's no module descriptor for your tests. Gradle may use --patch-module to add the tests to the module containing the production code.

This question and answer provides a lot of background information and possible fixes. As a short term fix, I recommend to add opens io.github.sskorol.testcases to your production code's module descriptor. Judging by its name, I'd guess there is no such package yet, so you'd either have to rename or add a dummy class (I would prefer the former).

I would also take this issue to a Gradle mailing list or bug tracker. Unless we've overlooked something (entirely possible), Gradle's behavior is very unfortunate because it would require adapting the production code's module descriptor to the test code's needs.

Source https://stackoverflow.com/questions/45673466

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install test-data-supplier

You can download it from GitHub, Maven.
You can use test-data-supplier like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the test-data-supplier component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .