scenario : We are in the integration testing phase . We would like to group all bugs in this phase on JIRA .
My problem : I wanted to create an epic called "testing phase" and group all bugs in the testing phase . But I also wanted to create a subgroup for "integration testing" and group all bugs in this integration testing phase . How do I do this .Can I use tasks under epic and do this ?
The Epic issue type (and a few others) are added to a base JIRA installation when you install the "JIRA Agile" extension/plugin. None of the features (Epic Links, Epics filtering on backlogs, Epic burndown charts, etc) will work with any other issue type.
chrome
Related
We have a requirement as below to automate in ZAP
Go through POST request in ZAP tool
Identify values which got posted in Request tab
Highlight the value passed(for example: to textarea field) and right click > goto Fuzzer
Choose required injections like SQL Injection or RDF Injection etc.,
Add payload
Start fuzzer
Expected result would be to generate a comparison report of request before and after fuzzing is done.
Can this be automated in ZAP?
Currently the Fuzzer doesn't have a web API. Largely due to the fact that we're lacking user input on how such functionality should work and what their expectations for it might be.
Here's the existing issue you should provide your feedback on: https://github.com/zaproxy/zaproxy/issues/1689
There is an unfinished PR adding an initial implementation, you could pull the PR branch and build the add-on for testing purposes and to potentially encourage the submitting user to complete it: https://github.com/zaproxy/zap-extensions/pull/2222
I'm creating a script that goes into all tests into a test execution. I'd like to get the amount of defects for that particular test execution. Is that a way to get it using rest api?
Xray enables exporting Cucumber tests to be exported as .feature file that further can be used in your automated tests. To do so use this export endpoint
To import the automated test results back to Jira used this import endpoint
Usually APIs will be executed in conjunction with CI/CD tools, like Jenkins.
In this article you can see that the total number of defects can be view via the Jira UI.
And finally, this video shows how tests are imported and exported via the UI.
Tests can be created via API as well, see here.
I think it all depends on your testplans. When those contain all tests you should be able to execute the test via the endpoint rest/raven/1.0/api/testexec/<testExecution>.
Maybe it will be good to ask the very same question in the atlassian community.
Sorry for not being able to fully answer your question, but I think you now should have some things to read :)
There is one way that is more straightforward.
You can make use of the "Test Execution Defects" custom field, which is a calculated field.
Then you just need to use Jira's REST API and obtain information for the related Test Execution issue, for that specific custom field that returns an array. The number of elements corresponds to the number of defects.
Example of HTTP GET request:
https://sandbox.xpand-it.com/rest/api/2/issue/BOOK-31?fields=customfield_11802
Example of response:
{
"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",
"id": "20130",
"self": "https://sandbox.xpand-it.com/rest/api/2/issue/20130",
"key": "BOOK-31",
"fields": {
"customfield_11802": [
"20131"
]
}
}
Another way would be to use the JQL function "defectsCreatedDuringTestExecution ()", as mentioned here: https://docs.getxray.app/display/XRAY/Enhanced+querying+with+JQL
Then you could do a Jira REST API search call.
Example of HTTP GET search request using the JQL function:
https://sandbox.xpand-it.com/rest/api/2/search?jql=issue%20in%20defectsCreatedDuringTestExecution(BOOK-31)
I have the next structure:
Bug
Dev task
Test Result with the failed test case
Tested by
For retest the bug I have created a RETEST task and link it to the bug. When I rerun the testcase I would like to add the passed test result to the RETEST task. How can I do? Or what is the best workflow?
You don't need to create a retest task for this case.
You could directly customize a workflow using States and Reasons for the Bug work item. Such as adding a state "Ready to Retest" for a Bug. And then assign this work item to the tester or tester group. Suggest you to use the Process Editor, available with the download of TFS Power Tools. The Process Template Editor provides a graphical user interface for customizing work items (field, workflow and the form) and process templates.
More ways for customize the workflow for a process please refer the tutorial from MSDN:
Customize the workflow for a process
Add or modify a work item type
Then you just need to directly link test result to the bug workitem. And in a Bug work item, you can click the HISTORY--ALL CAHNGES to track the history and process.
Just wondering how other people manage their test cases that are written for selenium test automation? I've been investigating maybe integrating with testlink to show the results and all, but I already have Jenkins set up for my environment and running my tests. What I'm really looking for is some way to nicely document my tests, like what steps each test performs for non-programmers.
I'm using Selenium with python, and Jenkins to run the tests.
I've tried two ways:
1) You can use Cucumber to write test steps like this:
#sanity #home_page #test_628
Scenario: Launch Support FAQs & Guides from Home cog
Given I navigate to Home page
When I click "Support" user logo link
Then I should see Support FAQs & Guides app launched
Each step written on Gherkin language (Given, When, Then) you can implement then using Selenium (I have to write on Ruby now, so I use Watir instead of Selenium).
see https://github.com/cucumber/cucumber/wiki/Python
2) But before that I used Robot Framework + Python + Selenium + Jenkins.
You can write test like this:
Go To Google Page [Documentation] Go to google page and search something
Open Browser to Google Page
Input Search selenium
Submit Search
This is done using human readable keywords. It prints very nice reports and can be easily integrated with Jenkins.
see http://www.wallix.org/2011/07/26/how-to-use-robotframework-with-the-selenium-library/
To document a test case and that too for non-programmers, Behaviour-Driven Development (BDD) is the best way. Some of the BDD tools are Cucumber, JBehave etc.
For example, lets assume the we have an website to manage some employees and we have a test case in which admin wants to add a new employee.
So the above test case can be documented using Cucumber as shown below:
Feature: Admin : Employees : Add Employees : Add Employee Details
Scenario: Verify that admin user is able to add new employee
Given Joe is an admin user
Given Joe is logged into the admin account
When Joe clicks "Add Emplyee" button
And Joe enters "Test Employee" in "Employee Name" text box
And Joe enters "12/05/1988" in "Birth Date" text box
And Joe selects "Male" from "Gender" radio button
And Joe clicks on "Submit" button
Then Joe gets message that says "Employee is added successfully."
The above test case can be easily understood by a non-programmer and he can perform each steps as performed by the test.
Hierarchy of folders for this test case will be feature/Admin/Employees/Add Employees/Add Employee Details
Hope this helps :)
I don't use TestLink. I think it is much easier to use a Jenkins job server to schedule my tests and it can do nearly the same job as testlink can and, im my opinion, is easier for other people to understand. I check my test code into Subversion and Jenkins checks out the latest code before it runs my tests. Jenkins has plugins to handle JUnit and TestNG report formats and has email capability, etc.
NOTE: The only Gotcha is that if you use RemoteWebDriver and a grid, the tests need to be ran by a Jenkins slave server that is running in a foreground process ( not in the background as a service). This is the case at least on Windows and might not be a problem on Linux.
We use Cucumber to create readable tests and have the results pulled back to Enterprise Tester, our Test Management platform. We can also pull Selenium tests and jUnit tests from Jenkins into Enterprise Tester, also for visibility across both manual and automated tests and traceability back to stories / requirements.
How is it possible to edit trac so a new ticket with component X follows workflow X and component Y follows workflow Y
Trac doesn't give you a way to do that at the moment. It assumes that your project has a single workflow.
There are some plugins that will give you additional workflow capabilities, however. The AdvancedTicketWorkflow Plugin gives you some advanced commands to use when designing your workflow. See the documentation for the "triage" command for an example of how to route two types of tickets through two slightly different workflows.
The TypedTicketWorkflow Plugin also adds additional workflow capabilities, by allowing you to create actions that are only applicable to certain ticket types.
There are a number of additional workflow-related plugins that you might want to test out. Some of them look like they haven't been updated in a while, though, so be aware that you may run into compatibility issues.