Download JAR files tagged by executed with all dependencies
cuneiform-dax from group de.hu-berlin.wbi.cuneiform (version 2.0.4-RELEASE)
Group: de.hu-berlin.wbi.cuneiform Artifact: cuneiform-dax
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact cuneiform-dax
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies cuneiform-core,
There are maybe transitive dependencies!
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies cuneiform-core,
There are maybe transitive dependencies!
cuneiform-starlinger from group de.hu-berlin.wbi.cuneiform (version 2.0.4-RELEASE)
Group: de.hu-berlin.wbi.cuneiform Artifact: cuneiform-starlinger
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact cuneiform-starlinger
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies cuneiform-core,
There are maybe transitive dependencies!
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies cuneiform-core,
There are maybe transitive dependencies!
cuneiform-addons from group de.hu-berlin.wbi.cuneiform (version 2.0.4-RELEASE)
Group: de.hu-berlin.wbi.cuneiform Artifact: cuneiform-addons
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact cuneiform-addons
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
cuneiform-core from group de.hu-berlin.wbi.cuneiform (version 2.0.4-RELEASE)
Group: de.hu-berlin.wbi.cuneiform Artifact: cuneiform-core
Show all versions Show documentation Show source
Show all versions Show documentation Show source
1 downloads
Artifact cuneiform-core
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 5
Dependencies antlr4, json, commons-logging, log4j, mockito-all,
There are maybe transitive dependencies!
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL Not specified
License not specified
Dependencies amount 5
Dependencies antlr4, json, commons-logging, log4j, mockito-all,
There are maybe transitive dependencies!
cuneiform from group de.hu-berlin.wbi.cuneiform (version 2.0.4-RELEASE)
A Functional Workflow Language.
Cuneiform is a workflow specification language which makes it easy to integrate heterogeneous tools and libraries and exploit data parallelism. Users do not have to create heavy-weight wrappers for establised tools or to reimplement them. Instead, they apply their existing software to partitioned data. Using the Hi-WAY application master Cuneiform can be executed on Hadoop YARN which makes it suitable for large scale data analysis.
Cuneiform comes in the form of a functional programming language with a Foreign Function Interface (FFI) that lets users create functions in any suitable scripting language and apply these functions in a uniform way.
Data paralelism is expressed by applying map, cross-product, dot-product, or combinations of the aforementioned algorithmic skeletons to collections of black-box data.
Group: de.hu-berlin.wbi.cuneiform Artifact: cuneiform
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact cuneiform
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL https://github.com/joergen7/cuneiform
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
Group de.hu-berlin.wbi.cuneiform
Version 2.0.4-RELEASE
Last update 17. May 2016
Organization not specified
URL https://github.com/joergen7/cuneiform
License Apache License, Version 2.0
Dependencies amount 0
Dependencies No dependencies
There are maybe transitive dependencies!
bte-parent from group gr.ekt.bte (version 0.9.3.5)
The biblio transformation engine is a java framework developed by the Hellenic National Documentation Centre (EKT, www.ekt.gr) and consists of programmatic APIs for filtering and modifying records that are retrieved from various types of data sources (eg. databases, files, legacy data sources) as well as for outputing them in appropriate standards formats (eg. database files, txt, xml, Excel). The framework includes independent abstract modules that are executed seperately, offering in many cases alternative choices to the user depending of the input data set, the transformation workflow that needs to be executed and the output format that needs to be generated.
Group: gr.ekt.bte Artifact: bte-parent
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact bte-parent
Group gr.ekt.bte
Version 0.9.3.5
Last update 05. October 2014
Organization not specified
URL http://github.com/EKT/Biblio-Transformation-Engine
License New BSD License
Dependencies amount 4
Dependencies log4j, dom4j, JUnitParams, mockito-core,
There are maybe transitive dependencies!
Group gr.ekt.bte
Version 0.9.3.5
Last update 05. October 2014
Organization not specified
URL http://github.com/EKT/Biblio-Transformation-Engine
License New BSD License
Dependencies amount 4
Dependencies log4j, dom4j, JUnitParams, mockito-core,
There are maybe transitive dependencies!
mocca-core from group de.ovgu.dke.mocca (version 0.1.2)
MOCCA is the Message-Oriented Command and Context Architecture,
providing a GLUE middle-ware that allows sending commands to a
peer which are executed by state-less handlers in a specific
context. In contrast to the Request-Response scheme the message
flow is not fixed by the framework. This allows to implement
different communication paradigms (including Request-Response).
The whole system can be seen as an automaton with Messages that
trigger state transitions in the local Contexts.
This library contains the core components, including the
GLUE-based implementation.
0 downloads
Artifact mocca-core
Group de.ovgu.dke.mocca
Version 0.1.2
Last update 16. April 2013
Organization not specified
URL https://projects.dke-research.de/redmine/projects/mocca/
License The Apache Software License, Version 2.0
Dependencies amount 3
Dependencies glue-core, glue-util, jcip-annotations,
There are maybe transitive dependencies!
Group de.ovgu.dke.mocca
Version 0.1.2
Last update 16. April 2013
Organization not specified
URL https://projects.dke-research.de/redmine/projects/mocca/
License The Apache Software License, Version 2.0
Dependencies amount 3
Dependencies glue-core, glue-util, jcip-annotations,
There are maybe transitive dependencies!
biblio-transformation-engine from group gr.ekt (version 0.82)
The biblio transformation engine is a java framework developed by the Hellenic National Documentation Centre (EKT, www.ekt.gr) and consists of programmatic APIs for filtering and modifying records that are retrieved from various types of data sources (eg. databases, files, legacy data sources) as well as for outputing them in appropriate standards formats (eg. database files, txt, xml, Excel). The framework includes independent abstract modules that are executed seperately, offering in many cases alternative choices to the user depending of the input data set, the transformation workflow that needs to be executed and the output format that needs to be generated.
Group: gr.ekt Artifact: biblio-transformation-engine
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact biblio-transformation-engine
Group gr.ekt
Version 0.82
Last update 21. September 2012
Organization not specified
URL biblio-transformation-engine.googlecode.com
License New BSD License
Dependencies amount 6
Dependencies dom4j, log4j, opencsv, jena, jxl, jbibtex,
There are maybe transitive dependencies!
Group gr.ekt
Version 0.82
Last update 21. September 2012
Organization not specified
URL biblio-transformation-engine.googlecode.com
License New BSD License
Dependencies amount 6
Dependencies dom4j, log4j, opencsv, jena, jxl, jbibtex,
There are maybe transitive dependencies!
idaithalam from group io.virtualan (version 1.7.0)
Idaithalam is a low code Test automation Framework, developed using Java and Cucumber. It leverages Behavior Driven Development (BDD). Tester can create test cases/scripts in simple Excel with API Spec. Excel is a simplified way to create Json based test scripts in Idaithalam. Test cases can be created quickly and tested in minutes.
As a tester, you need to create Excel and pass it to Idaithalam Framework.
First, generate the Json based test scripts(Virtualan Collection) from Excel. During test execution, this test script collection can be directly utilized.
Then it generates Feature files from the Virtualan Collection and its executed.
Lastly, It generates test report in BDD/Cucumber style.
This provide complete testing support for REST APIs, GraphQL, RDBMS DB and Kafka Event messages
#idaithalam #apitesting #testautomation #restapitesting #insprintautomation #rdbmstesting #graphqltesting #kafkamessagetesting #eventvalidation #messagevalidation #cucumber #bdd
Virtualan Collection is a JSON based TestScripts generated from Excel
API testing can be automated using Excel, POSTMAN collection and VIRTUALAN
- Utilized for API testing.
- Utilized Contract testing.
- Utilized Production Checkout.
- Agile Testing - Progressive Regression can be done for each sprint. Reduce lot of manual effects.
0 downloads
Artifact idaithalam
Group io.virtualan
Version 1.7.0
Last update 23. May 2022
Organization not specified
URL https://www.virtualan.io
License Apache License 2.0
Dependencies amount 12
Dependencies cucumblan-api, cucumblan-db, cucumblan-message, jackson-databind, commons-lang3, commons-io, cucumber-reporting, compiler, gherkin-formatter, slf4j-simple, log4j-core, swagger-inflector,
There are maybe transitive dependencies!
Group io.virtualan
Version 1.7.0
Last update 23. May 2022
Organization not specified
URL https://www.virtualan.io
License Apache License 2.0
Dependencies amount 12
Dependencies cucumblan-api, cucumblan-db, cucumblan-message, jackson-databind, commons-lang3, commons-io, cucumber-reporting, compiler, gherkin-formatter, slf4j-simple, log4j-core, swagger-inflector,
There are maybe transitive dependencies!
pact-jvm-provider-junit5_2.11 from group au.com.dius (version 3.5.24)
# Pact Junit 5 Extension
## Overview
For writing Pact verification tests with JUnit 5, there is an JUnit 5 Invocation Context Provider that you can use with
the `@TestTemplate` annotation. This will generate a test for each interaction found for the pact files for the provider.
To use it, add the `@Provider` and one of the pact source annotations to your test class (as per a JUnit 4 test), then
add a method annotated with `@TestTemplate` and `@ExtendWith(PactVerificationInvocationContextProvider.class)` that
takes a `PactVerificationContext` parameter. You will need to call `verifyInteraction()` on the context parameter in
your test template method.
For example:
```java
@Provider("myAwesomeService")
@PactFolder("pacts")
public class ContractVerificationTest {
@TestTemplate
@ExtendWith(PactVerificationInvocationContextProvider.class)
void pactVerificationTestTemplate(PactVerificationContext context) {
context.verifyInteraction();
}
}
```
For details on the provider and pact source annotations, refer to the [Pact junit runner](../pact-jvm-provider-junit/README.md) docs.
## Test target
You can set the test target (the object that defines the target of the test, which should point to your provider) on the
`PactVerificationContext`, but you need to do this in a before test method (annotated with `@BeforeEach`). There are three
different test targets you can use: `HttpTestTarget`, `HttpsTestTarget` and `AmpqTestTarget`.
For example:
```java
@BeforeEach
void before(PactVerificationContext context) {
context.setTarget(HttpTestTarget.fromUrl(new URL(myProviderUrl)));
// or something like
// context.setTarget(new HttpTestTarget("localhost", myProviderPort, "/"));
}
```
## Provider State Methods
Provider State Methods work in the same way as with JUnit 4 tests, refer to the [Pact junit runner](../pact-jvm-provider-junit/README.md) docs.
## Modifying the requests before they are sent
**Important Note:** You should only use this feature for things that can not be persisted in the pact file. By modifying the request, you are potentially modifying the contract from the consumer tests!
Sometimes you may need to add things to the requests that can't be persisted in a pact file. Examples of these would be authentication tokens, which have a small life span. The Http and Https test targets support injecting the request that will executed into the test template method.
You can then add things to the request before calling the `verifyInteraction()` method.
For example to add a header:
```java
@TestTemplate
@ExtendWith(PactVerificationInvocationContextProvider.class)
void testTemplate(PactVerificationContext context, HttpRequest request) {
// This will add a header to the request
request.addHeader("X-Auth-Token", "1234");
context.verifyInteraction();
}
```
## Objects that can be injected into the test methods
You can inject the following objects into your test methods (just like the `PactVerificationContext`). They will be null if injected before the
supported phase.
| Object | Can be injected from phase | Description |
| ------ | --------------- | ----------- |
| PactVerificationContext | @BeforeEach | The context to use to execute the interaction test |
| Pact | any | The Pact model for the test |
| Interaction | any | The Interaction model for the test |
| HttpRequest | @TestTemplate | The request that is going to be executed (only for HTTP and HTTPS targets) |
| ProviderVerifier | @TestTemplate | The verifier instance that is used to verify the interaction |
Group: au.com.dius Artifact: pact-jvm-provider-junit5_2.11
Show all versions Show documentation Show source
Show all versions Show documentation Show source
2 downloads
Artifact pact-jvm-provider-junit5_2.11
Group au.com.dius
Version 3.5.24
Last update 04. November 2018
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies kotlin-stdlib-jdk8, kotlin-reflect, slf4j-api, groovy-all, kotlin-logging, scala-library, scala-logging_2.11, pact-jvm-provider-junit_2.11, junit-jupiter-api,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.5.24
Last update 04. November 2018
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 9
Dependencies kotlin-stdlib-jdk8, kotlin-reflect, slf4j-api, groovy-all, kotlin-logging, scala-library, scala-logging_2.11, pact-jvm-provider-junit_2.11, junit-jupiter-api,
There are maybe transitive dependencies!
Page 26 from 28 (items total 277)