java.lang.NoClassDefFoundError: groovy/lang/GroovyObject (issue for Rest Assured project in Eclipse)

Code:

import org.testng.annotations.Test;

import io.restassured.RestAssured;

import io.restassured.response.Response;

public class AppTest {

@Test

public void test_01() {

Response response = RestAssured.get("https://reqres.in/api/users?page=2");

System.out.println(response.getStatusCode());

System.out.println(response.getTime());

}

}

......................................................................................................................

Error message:

[RemoteTestNG] detected TestNG version 6.14.3

FAILED: test_01

java.lang.NoClassDefFoundError: groovy/lang/GroovyObject

at java.lang.ClassLoader.defineClass1(Native Method)

at java.lang.ClassLoader.defineClass(Unknown Source)

at java.security.SecureClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.access$100(Unknown Source)

at java.net.URLClassLoader$1.run(Unknown Source)

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at io.restassured.RestAssured.<clinit>(RestAssured.java:355)

at AppTest.test_01(AppTest.java:10)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:124)

at org.testng.internal.Invoker.invokeMethod(Invoker.java:583)

at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:719)

at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:989)

at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)

at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)

at org.testng.TestRunner.privateRun(TestRunner.java:648)

at org.testng.TestRunner.run(TestRunner.java:505)

at org.testng.SuiteRunner.runTest(SuiteRunner.java:455)

at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:450)

at org.testng.SuiteRunner.privateRun(SuiteRunner.java:415)

at org.testng.SuiteRunner.run(SuiteRunner.java:364)

at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)

at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:84)

at org.testng.TestNG.runSuitesSequentially(TestNG.java:1208)

at org.testng.TestNG.runSuitesLocally(TestNG.java:1137)

at org.testng.TestNG.runSuites(TestNG.java:1049)

at org.testng.TestNG.run(TestNG.java:1017)

at org.testng.remote.AbstractRemoteTestNG.run(AbstractRemoteTestNG.java:114)

at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:251)

at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:77)

Caused by: java.lang.ClassNotFoundException: groovy.lang.GroovyObject

at java.net.URLClassLoader$1.run(Unknown Source)

at java.net.URLClassLoader$1.run(Unknown Source)

at java.security.AccessController.doPrivileged(Native Method)

at java.net.URLClassLoader.findClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)

at java.lang.ClassLoader.loadClass(Unknown Source)

... 39 more

Caused by: java.util.zip.ZipException: invalid LOC header (bad signature)

at java.util.zip.ZipFile.read(Native Method)

at java.util.zip.ZipFile.access$1400(Unknown Source)

at java.util.zip.ZipFile$ZipFileInputStream.read(Unknown Source)

at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(Unknown Source)

at java.util.zip.InflaterInputStream.read(Unknown Source)

at java.util.jar.Manifest$FastInputStream.fill(Unknown Source)

at java.util.jar.Manifest$FastInputStream.readLine(Unknown Source)

at java.util.jar.Manifest$FastInputStream.readLine(Unknown Source)

at java.util.jar.Attributes.read(Unknown Source)

at java.util.jar.Manifest.read(Unknown Source)

at java.util.jar.Manifest.<init>(Unknown Source)

at java.util.jar.JarFile.getManifestFromReference(Unknown Source)

at java.util.jar.JarFile.getManifest(Unknown Source)

at sun.misc.URLClassPath$JarLoader$2.getManifest(Unknown Source)

at java.net.URLClassLoader.defineClass(Unknown Source)

at java.net.URLClassLoader.access$100(Unknown Source)

... 46 more

===============================================

    Default test

    Tests run: 1, Failures: 1, Skips: 0

===============================================

===============================================

Default suite

Total tests run: 1, Failures: 1, Skips: 0

===============================================

.............................. Looking for solution...............................................................


Comments

Post a Comment

Popular posts from this blog

What is Smoke testing

Smoke testing is a type of software testing that is conducted to check whether the basic functionality of the software application is working or not. It is a preliminary test that is conducted to ensure that the critical components of the software system are functioning correctly after any major changes or updates. The term "smoke testing" comes from the idea of testing the software application just like a smoke test is done to check whether a machine is working or not. Smoke testing is performed after the build process to determine whether the build is stable enough for further testing. The main objective of smoke testing is to detect the major defects or errors that can cause the system to crash or not function correctly. It is a quick and easy test that is designed to identify any critical issues before proceeding with further testing. Smoke testing involves executing a few basic tests on the application, such as opening the application, logging in, navigating to different
Read more

Examples of Sanity testing

Examples of sanity testing: Web Application : In the case of a web application, sanity testing can involve testing the specific modules or functionalities that have been added or modified. For example, if a new payment gateway has been integrated into the application, sanity testing will focus on verifying whether the payment gateway is working correctly, the payment data is being stored securely, and the transaction is being processed without any errors. Mobile Application : In the case of a mobile application, sanity testing can involve testing the new features or modifications that have been made to the application. For example, if a new feature for push notifications has been added to the application, sanity testing will focus on verifying whether the notifications are being sent correctly, the notifications are being received on time, and the user can disable the notifications if required. API : In the case of an API, sanity testing can involve testing the new endpoints or modific
Read more