ReadyAPI - Jira Integration
I am attempting to use the Jira plugin and have it setup. I have the connections configured and they are working. However, when trying to create a new Jira item, the screen displayed does not have all the needed information. Looking at the wiki for the plugin, the screen shots for creating a new Jira item have a lot more information than I am seeing. The connection to Jira is fine as I am able to click the Jira icon from a test case and select my project. It also is retrieving the issue types correctly from Jira. However, when filling out the Summary, which is the only required field displayed to me, the creation of the item fails because it is missing more required information. Jira version = 9.12.15 ReadyAPI Version = 3.58.0 Jira plugin version = 1.6.7 There are no errors in the error log. The only "error" I see is in the HTTP log after the creation of the Jira item fails: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={customfield_10010=Acceptance Criteria is required., customfield_11200=Category is required.}, errorMessages=[]}]} In the ReadyAPI log, I see some records like this. It seems to be getting all the fields from Jira, but even after it checks for it, it still just displays the issue type. For example, there are the lines where it appears to find the "description" field. Attached a screen shot of the "Create Story" screen. Any help or guidance would be appreciated. Tue Feb 25 12:47:33 CST 2025: INFO: getFieldInfo.bugTrackerProvider : com.smartbear.ready.plugin.jira.impl.JiraProvider@4a9b76c, selectedProject : EWS, fieldInfoKey: description Tue Feb 25 12:47:33 CST 2025: INFO: [JiraProvider].[getProjectFieldsInternal] we reach here Tue Feb 25 12:47:33 CST 2025: INFO: getFieldInfo.bugTrackerProvider : com.smartbear.ready.plugin.jira.impl.JiraProvider@4a9b76c, selectedProject : EWS, fieldInfoKey: description Tue Feb 25 12:47:33 CST 2025: INFO: [JiraProvider].[getProjectFieldsInternal] we reach here Tue Feb 25 12:47:48 CST 2025: INFO: [CreateIssueMetadataJsonParserExt].[parse] json: {"maxResults":50,"startAt":0,"total":16,"isLast":true,"values":[{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/1","id":"1","description":"A problem which impairs or prevents the functions of the product.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Bug","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10100","id":"10100","description":"Spikes are a type of story used for activities such as research, design, exploration, or prototyping. They are used to gain knowledge in order to reduce risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/exclamation.png","name":"Spike","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10300","id":"10300","description":"This subtask represents a defect found during testing or review of a Story","iconUrl":"https:\/\/jira\/images\/icons\/subtask-defect.png","name":"Defect","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10400","id":"10400","description":"An impediment is anything that is slowing or stopping the team(s) or effort down.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/delete.png","name":"Impediment","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10700","id":"10700","description":"An announcement of information that is not an impediment or risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/blank.png","name":"Notification","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10701","id":"10701","description":"Any uncertain event that can have an impact on the success.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Risk","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10702","id":"10702","description":"Use for technical analysis, research work done by team member for detail design type work. ","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Technical Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10703","id":"10703","description":"Use for solution analysis, work done by team member for defining and clarifying discovery efforts, requirements, MBI\/MTI and features. Mainly used by solution analysts.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Solution Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10804","id":"10804","description":"This is an \"initial placeholder\" issue and optional to use. It generally only includes the summary and possibly a supporting sentence or two","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=14404&avatarType=issuetype","name":"Raw","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/3","id":"3","description":"A task that needs to be done.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13818&avatarType=issuetype","name":"Task","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/4","id":"4","description":"An improvement or enhancement to an existing feature or task.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13810&avatarType=issuetype","name":"Improvement","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/5","id":"5","description":"The sub-task of the issue","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13816&avatarType=issuetype","name":"Sub-task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/6","id":"6","description":"Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=15719&avatarType=issuetype","name":"Feature","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/7","id":"7","description":"Created by Jira Software - do not edit or delete. Issue type for a user story.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13815&avatarType=issuetype","name":"Story","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/8","id":"8","description":"Created by GreenHopper - do not edit or delete. Issue type for a technical task.","iconUrl":"https:\/\/jira\/images\/icons\/ico_task.png","name":"Technical task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/9","id":"9","description":"Unit, Behavior, or Test Case","iconUrl":"https:\/\/jira\/images\/icons\/chem.png","name":"Test task","subtask":true}]} Tue Feb 25 12:47:48 CST 2025: INFO: [CreateIssueMetadataJsonParserExt].[parse] json: {"maxResults":50,"startAt":0,"total":16,"isLast":true,"values":[{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/1","id":"1","description":"A problem which impairs or prevents the functions of the product.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Bug","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10100","id":"10100","description":"Spikes are a type of story used for activities such as research, design, exploration, or prototyping. They are used to gain knowledge in order to reduce risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/exclamation.png","name":"Spike","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10300","id":"10300","description":"This subtask represents a defect found during testing or review of a Story","iconUrl":"https:\/\/jira\/images\/icons\/subtask-defect.png","name":"Defect","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10400","id":"10400","description":"An impediment is anything that is slowing or stopping the team(s) or effort down.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/delete.png","name":"Impediment","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10700","id":"10700","description":"An announcement of information that is not an impediment or risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/blank.png","name":"Notification","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10701","id":"10701","description":"Any uncertain event that can have an impact on the success.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Risk","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10702","id":"10702","description":"Use for technical analysis, research work done by team member for detail design type work. ","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Technical Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10703","id":"10703","description":"Use for solution analysis, work done by team member for defining and clarifying discovery efforts, requirements, MBI\/MTI and features. Mainly used by solution analysts.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Solution Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10804","id":"10804","description":"This is an \"initial placeholder\" issue and optional to use. It generally only includes the summary and possibly a supporting sentence or two","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=14404&avatarType=issuetype","name":"Raw","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/3","id":"3","description":"A task that needs to be done.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13818&avatarType=issuetype","name":"Task","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/4","id":"4","description":"An improvement or enhancement to an existing feature or task.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13810&avatarType=issuetype","name":"Improvement","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/5","id":"5","description":"The sub-task of the issue","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13816&avatarType=issuetype","name":"Sub-task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/6","id":"6","description":"Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=15719&avatarType=issuetype","name":"Feature","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/7","id":"7","description":"Created by Jira Software - do not edit or delete. Issue type for a user story.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13815&avatarType=issuetype","name":"Story","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/8","id":"8","description":"Created by GreenHopper - do not edit or delete. Issue type for a technical task.","iconUrl":"https:\/\/jira\/images\/icons\/ico_task.png","name":"Technical task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/9","id":"9","description":"Unit, Behavior, or Test Case","iconUrl":"https:\/\/jira\/images\/icons\/chem.png","name":"Test task","subtask":true}]}JDBC "Some connection settings are not specified"
I am trying to connect to a sql database using the jdbc driver. I have the connection setup but when I try to send a request, if I use my global database connection I receive an error message stating "Some connection settings are not specified", but if I use the exact same connection string built inside the JDBC request, my test connection works and I am able to query the database. Does anyone know what settings are possibly missing/misconfigured? I dont know of any reason the global db connection would fail while the same connection string works inside the jdbc request. Screenshots attached
Is it possible to integrate the Azure TestPlan Test cases and the ReadyAPI tests ?
I have created manual test cases in Azure devops Test Plan. I have automated the manual test case functionality using ReadyAPI. Now i want to link the Azure Test Plan test cases while running the ReadyAPI tests via the Azure pieplines. Is it possible to do so ? I am using the Azure devops extension named "ReadyAPI Test for Azure Devops" and "Publish Test Results" in my pipeline.radyapi maven integration
I am using maven version 3.9.5 and would like to integrate with readyapi by following instructions from here https://support.smartbear.com/readyapi/docs/integrations/junit.html but it seems not working. Any help how I can integrate readyapi project with maven versions 3.** Thanks in advance here is my pom.xml <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.example.pr</groupId> <artifactId>readyapi</artifactId> <version>0.0.1</version> <packaging>jar</packaging> <properties> <java.version>11</java.version> </properties> <repositories> <repository> <id>SmartBearPluginRepository</id> <url>http://smartbearsoftware.com/repository/maven2</url> </repository> </repositories> <dependencies> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.4.11</version> </dependency> <dependency> <groupId>com.oracle.database.jdbc</groupId> <artifactId>ojdbc10</artifactId> <version>19.20.0.0</version> </dependency> <dependency> <groupId>org.springframework</groupId> <artifactId>spring-jdbc</artifactId> <version>5.3.29</version> </dependency> <!-- https://mvnrepository.com/artifact/io.github.openfeign/feign-core --> <dependency> <groupId>io.github.openfeign</groupId> <artifactId>feign-core</artifactId> <version>12.5</version> </dependency> <!-- https://mvnrepository.com/artifact/io.github.openfeign/feign-jackson --> <dependency> <groupId>io.github.openfeign</groupId> <artifactId>feign-jackson</artifactId> <version>12.5</version> </dependency> <dependency> <groupId>io.github.openfeign</groupId> <artifactId>feign-hc5</artifactId> <version>12.5</version> </dependency> <dependency> <groupId>com.fasterxml.jackson.core</groupId> <artifactId>jackson-databind</artifactId> <version>2.15.3</version> </dependency> <!-- https://mvnrepository.com/artifact/org.junit.jupiter/junit-jupiter-api --> <dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter-api</artifactId> <version>5.10.0</version> <scope>test</scope> </dependency> <!-- https://mvnrepository.com/artifact/com.appland/appmap-agent --> <dependency> <groupId>com.appland</groupId> <artifactId>appmap-agent</artifactId> <version>1.26.1</version> <scope>runtime</scope> </dependency> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.13.2</version> <scope>test</scope> </dependency> <!-- <dependency>--> <!-- <groupId>org.mockito</groupId>--> <!-- <artifactId>mockito-all</artifactId>--> <!-- <version>1.10.19</version>--> <!-- <scope>test</scope>--> <!-- </dependency>--> <dependency> <groupId>org.mockito</groupId> <artifactId>mockito-core</artifactId> <version>4.2.0</version> <scope>test</scope> </dependency> <!-- Used to combine JUnit 5 with Mockito --> <dependency> <groupId>org.mockito</groupId> <artifactId>mockito-junit-jupiter</artifactId> <version>4.2.0</version> <scope>test</scope> </dependency> <dependency> <groupId>com.smartbear</groupId> <artifactId>ready-api-maven-plugin</artifactId> <version>2.7.0</version> <exclusions> <exclusion> <groupId>com.google.guava</groupId> <artifactId>guava</artifactId> </exclusion> </exclusions> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>11</source> <target>11</target> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-shade-plugin</artifactId> <version>3.4.1</version> <configuration> <finalName>${project.artifactId}</finalName> </configuration> <executions> <execution> <phase>package</phase> <goals> <goal>shade</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </project>How to get ReadyAPI Maven runner to detect new login license?
Our workplace has officially moved over to the new licenses that you have to login to authenticate with. I've had no problems using it with the ReadyAPI GUI but when I try to run automation through Java on the command line using the Maven runner, it doesn't detect my license. What needs to be done to allow the Java and Maven to see that I am a licensed user? Thanks for your help.
