You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -323,8 +323,8 @@ For teams familiar with or currently using [REST-assured](http://rest-assured.io
323
323
324
324
## References
325
325
*[API Testing with Karate](https://youtu.be/WT4gg7Jutzg) - video + demos by [Peter Thomas](https://twitter.com/ptrthomas) (creator / lead dev of Karate)
326
-
*[Intro to all features of Karate](https://youtu.be/yu3uupBZyxc) - video + demos by [Peter Thomas](https://twitter.com/ptrthomas) (creator / lead dev of Karate)
327
-
*[Karate entered the ThoughtWorks Tech Radar](https://twitter.com/KarateDSL/status/1120985060843249664)in 2019 and was [upgraded in ranking](https://twitter.com/KarateDSL/status/1262719979104817152) in May 2020
326
+
*[Introducing Karate: The ULTIMATE Test Automation Tool](https://youtu.be/_kMxvd37auc?si=WOEkvEUH6eWeHZUC) - video by [James Willett](https://www.linkedin.com/in/willettjames/)
327
+
*[Karate in the ThoughtWorks Tech Radar](https://twitter.com/KarateDSL/status/1120985060843249664) and featured [a second time](https://twitter.com/KarateDSL/status/1262719979104817152)
328
328
*[マイクロサービスにおけるテスト自動化 with Karate](https://speakerdeck.com/takanorig/microservices-testing-automation-with-karate) - (*Microservices Test Automation with Karate*) presentation by [Takanori Suzuki](https://twitter.com/takanorig)
329
329
*[Writing API Tests with Karate](https://www.softwaretester.blog/writing-api-tests-with-karate) - book by [Benjamin Bischoff](https://www.softwaretester.blog/about), Packt Publishing, 2023
330
330
*[Karate Webinar](https://www.youtube.com/watch?v=cXDIYpT6zck&t=4333s) - Simplificando automação de API com Karate Framework by [Luana Assis](https://www.linkedin.com/in/luanapassis/) from [Base2 Tecnologia](https://www.base2.com.br/)
@@ -334,7 +334,7 @@ Karate also has a dedicated "tag", and a very active and supportive community at
334
334
You can find a lot more references, tutorials and blog-posts at [karatelabs.io](https://karatelabs.io).
335
335
336
336
# Getting Started
337
-
If you are a Java developer - Karate requires at least [Java](http://www.oracle.com/technetwork/java/javase/downloads/index.html)11 and then either [Maven](http://maven.apache.org), [Gradle](https://gradle.org), or a Java IDE that embeds either to be installed. Note that Karate works fine on OpenJDK.
337
+
If you are a Java developer - Karate requires at least [Java](http://www.oracle.com/technetwork/java/javase/downloads/index.html)17 and then either [Maven](http://maven.apache.org), [Gradle](https://gradle.org), or a Java IDE that embeds either to be installed. Note that Karate works fine on OpenJDK.
338
338
339
339
If you are new to programming or test-automation, the [official IntelliJ plugin](https://plugins.jetbrains.com/plugin/19232-karate) is recommended.
340
340
@@ -347,9 +347,9 @@ All you need is available in the [`karate-core`](https://search.maven.org/artifa
347
347
348
348
```xml
349
349
<dependency>
350
-
<groupId>com.intuit.karate</groupId>
350
+
<groupId>io.karatelabs</groupId>
351
351
<artifactId>karate-junit5</artifactId>
352
-
<version>1.4.1</version>
352
+
<version>1.5.0</version>
353
353
<scope>test</scope>
354
354
</dependency>
355
355
```
@@ -358,7 +358,7 @@ All you need is available in the [`karate-core`](https://search.maven.org/artifa
Also refer to the wiki for using [Karate with Gradle](https://github.com/karatelabs/karate/wiki/Gradle).
@@ -372,7 +372,7 @@ For example when using Maven:
372
372
373
373
```xml
374
374
<dependency>
375
-
<groupId>com.intuit.karate</groupId>
375
+
<groupId>io.karatelabs</groupId>
376
376
<artifactId>karate-core</artifactId>
377
377
<version>${karate.version}</version>
378
378
<classifier>all</classifier>
@@ -391,9 +391,9 @@ You can replace the values of `com.mycompany` and `myproject` as per your needs.
391
391
392
392
```
393
393
mvn archetype:generate \
394
-
-DarchetypeGroupId=com.intuit.karate \
394
+
-DarchetypeGroupId=io.karatelabs \
395
395
-DarchetypeArtifactId=karate-archetype \
396
-
-DarchetypeVersion=1.4.1 \
396
+
-DarchetypeVersion=1.5.0 \
397
397
-DgroupId=com.mycompany \
398
398
-DartifactId=myproject
399
399
```
@@ -444,9 +444,6 @@ With the above in place, you don't have to keep switching between your `src/test
444
444
445
445
Once you get used to this, you may even start wondering why projects need a `src/test/resources` folder at all !
446
446
447
-
### Spring Boot Example
448
-
[Soumendra Daas](https://twitter.com/sdaas) has created a nice example and guide that you can use as a reference here: [`hello-karate`](https://github.com/Sdaas/hello-karate). This demonstrates a Java Maven + JUnit 5 project set up to test a [Spring Boot](http://projects.spring.io/spring-boot/) app.
449
-
450
447
## Naming Conventions
451
448
Since these are tests and not production Java code, you don't need to be bound by the `com.mycompany.foo.bar` convention and the un-necessary explosion of sub-folders that ensues. We suggest that you have a folder hierarchy only one or two levels deep - where the folder names clearly identify which 'resource', 'entity' or API is the web-service under test.
Copy file name to clipboardExpand all lines: examples/gatling/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
# karate-gatling-demo
2
2
demo sample project for karate [test-doubles](https://github.com/karatelabs/karate/tree/master/karate-netty) and [gatling integration](https://github.com/karatelabs/karate/tree/master/karate-gatling)
3
3
4
+
> Another example which demos the use of the Java DSL instead of Scala can be found here: [karate-todo](https://github.com/karatelabs/karate-todo).
0 commit comments