Software Testing Tutorial
- Introduction to Software Testing
- Principles of Software Testing
- Software Development Life Cycle (SDLC)
- Software Testing Life Cycle (STLC)
- Levels of Testing
- Database Testing
- Ad-hoc Testing
- Testing Types
- Test Closure Report Preparation
- Test Report Preparation
- ISTQB Organization and Certification Overviews
- JIRA Interview Questions and Answers
- Applications of Jira
- Installation of Jira
- Kanban Board In Jira
- Kanban Tool
- Jira Scrum Board/
- Difference Between Scrum Board Vs Kanban Board
- JIRA Bug Life Cycle
- JIRA Versions
- JIRA Workflow
- JIRA Dashboard
- Sprint in JIRA
- JIRA Epic
- Backlog in JIRA
- JIRA Testing Tool
- Difference between JIRA and Bugzilla
- INSTALLATION OF TENSORFLOW
JIRA Interview Questions and Answers
What is JIRA?
JIRA is an issue tracking product developed by Atlassian which allows bug tracking and agile project management. The name “JIRA” is inherited from the word Gojira, the Japanese word for Godzilla, which is a reference to a competitor Bugzilla.
Why is JIRA used?
Atlassian JIRA is an issue tracking and agile project management tool which allows us to track any project by following a proper workflow. Following are the reasons behind using JIRA.
- JIRA is a platform independent that could run anywhere
- JIRA can be run anywhere
- In JIRA, a workflow can be easily customized based on our requirement
- JIRA acts as an issue tracking as well as project management tool
- JIRA allows us to track the progress of a project from time to time
What are the differences between JIRA and Bugzilla?
JIRA and Bugzilla are the two bug tracking tools that are widely being used by several organizations for quite some time now.
JIRA Bugzilla JIRA is a commercial tool Bugzilla is an open source tool JIRA is a user friendly tool compared to Bugzilla Bugzilla is not so friendly tool compared to JIRA Drag and drop issue prioritization is available in JIRA Drag and drop issue prioritization is not available in Bugzilla JIRA has configurable link types with user-defined semantics. JIRA also has pluggable remote issue links, that allow to link an issue to any other entity outside JIRA Bugzilla has only one link type: blocks/depends, plus a Bug ID custom field Unlike Bugzilla, JIRA allows to define multiple workflows which are applied based on the issue’s Project and Type Unlike JIRA, Bugzilla can let users select the initial status of a new issue Custom field types available in JIRA are too many to list, and even more custom field types available from plugins Custom field types available in Bugzilla are Text fields, Multi-selection, Drop-down, Date/time, Bug ID JIRA allows conditional configuration based only on Project and Type fields Bugzilla lets you show/hide the whole custom field or specific values based on the value of some other field JIRA lacks advance-level search options. JIRA has flexible JQL language (JIRA Query Language) that allows you to build arbitrary boolean expressions Bugzilla’s comes with a powerful advanced search option
Can Jira be used for test case management?
Although JIRA was not designed to serve as a Test Case Management, it can be configured to support test case management in two different ways. You can either change native components in JIRA to meet test case management needs or you can use one of the add-ons available in Atlassian Marketplace (Example: Zephyr of JIRA).
What is a workflow in JIRA?
Workflow is defined as a series of sequential tasks that need to be completed in order to reach a certain goal.
A workflow in JIRA is defined as a series of sequential tasks (such as create/open a bug, Work in progress, and completed/closed) involved in the life cycle of a bug or an issue.
Create an issue or bug
Work in progress:
Series of actions performed to fix the issue
Completion of the issue after verification
What are the limitations when editing an active workflow?
Limitations apply when editing the draft for an active workflow:
- It is not possible to edit the workflow name
- Workflow statuses cannot be deleted
- If a status has no outgoing transitions, it cannot have any outgoing transitions added, regular or global
- The step ID cannot be changed
What is a Workflow designer in JIRA?
The workflow designer in JIRA is a graphical tool that enables you to see the layout of your workflow and to create and modify a workflow’s procedures and transitions.
- You can manage status and transitions: add, click and drag, or select to edit properties to rename, or delete
- You can add a global transition that permits different status in the workflow to transition to the selected status. Select Allow all statuses to transition to this one in the properties board for the transition.
- You can change the screen that a transition uses.
- You can configure advanced transition options such as conditions, triggers, validators, and post functions.
How does a service desk work in JIRA?
Here is how Customers and Service desk agents work together to resolve a request in JIRA.
- Your customer submits a request to service agents through a portal or by email
- Service desk agents see the request in their JIRA Service Desk line and investigate the issue.
- Your customer and other participants utilize the portal or email to discuss the request with service desk agent, who works in JIRA Service Desk.
- Your service agent completes the request and your customer is satisfied.
How are reports generated in JIRA?
Steps to follow to generate reports in JIRA are as follows:
Navigate to the desired board and click Reports. You can find different types of reports.
Click Switch report to view a different report.
Click on the switch report option to view a different report
What are the types of reports generated in JIRA?
JIRA provides different types of reports within a project which are used to show the project statistics throughout the project life cycle. There are reports to analyze issues as well as reports for Scrum and Kanban projects.
Name some reports generated by Kanban projects in JIRA.
The reports generated by any Kanban project in JIRA are
- Control chart
- Cumulative Flow diagram
Name some reports generated by Scrum projects in JIRA.
The reports generated by any Scrum project in JIRA are
- Sprint Report
- Control chart
- Burn down chart
- Cumulative Flow diagram
- Epic Report
- Release Burndown
- Velocity chart
- Version Report
Name some reports generated in JIRA for the issues tracking and analysis.
Following are the general reports generated as and when required for analyzing issues:
- Average Age Report
- Created vs Resolved issue Report
- Pie Chart Report
- Recently created Issue Report
- Resolution Time Report
- Time Tracking Report
- User Work load Report
- Version Work load Report
- Workload Pie chart Report
What is an issue in JIRA?
Different organizations use JIRA to track various types of issues, which can represent anything from a software bug, to a project task, or a leave request form.
Issues are the building blocks of any JIRA project. An issue could represent a story, a bug, a task, or another issue type in your project.
Explain how an issue is created in JIRA.
Let’s see step by step how an issue is created in Atlassian JIRA.
- Click Create at the top of the screen to open the Create Issue dialog box.
- Select the relevant Project and Issue Type in the Create Issue dialog box.
- Type a Summary for the issue and complete any appropriate fields (required fields are marked by an asterisk)
Note: Make sure you check they’re all correct before creating the next issue.
- When you are satisfied with the content of your issue, click the Create button.
What are the color indicators in JIRA and mention their significance?
There are three color (Blue, Orange & Green) indicators in JIRA. Issue tracking becomes easy with different color representation. These three colors are used to denote the amount of time spent on any particular issue.
Blue color denotes Original Estimate i.e., the estimated time to resolve an issue
Orange color denotes Remaining Estimate i.e., the remaining time to resolve an issue
Green color denotes Time spent or Logged i.e., the total time spent to resolve the issue
How to view change history for any issue in JIRA?
The change history for any issue can be viewed in JIRA by following steps:
- Open any issue.
- Click on ‘History’ tab present in the ‘Activity’ section.
How an issue can be shared in JIRA with other users?
There is a share option available on the issue description page in JIRA. An issue can be shared with other users using this share option. Once a share option is clicked, it will ask you to provide “Username or Email” and “Note”
Why an issue is labeled in JIRA?
Labeling an issue in JIRA allows you to find which category an issue belongs to. Issues can be easily searched with the help of labels. Labels can be initially set at the time of creating the issue. It can also be modified if required.
How is an issue linked in JIRA?
Linking means establishing the relationship between the two. In JIRA, an issue can be linked with other issues on either the same or different JIRA servers.
An issue can be linked with other issues as follows
- An issue may relate to another issue
- An issue may duplicate another issue
- An issue may block another issue
What is the use of Move Issue wizard in JIRA?
Move Issue wizard enables you to specify another project in your JIRA instance. The Move Issue wizard permits you to change certain attributes of the issue such as Issue Type, Issue Status, and Custom Fields.
If your issue is a custom issue type that does not exist in your target project, you must choose a new issue type.
If you have assigned a custom status to your issue, and it does not exist in your target project, you must select a new issue status for your issue.
If you have defined required custom fields for your issue that does not exist in your target project, you must set values for them.
How to schedule an issue in JIRA?
To schedule an issue, populate its Due date field. This can be done either when creating an issue, or at a later stage by editing the issue. Only users with the schedule issues permission can populate the Due date field.
How project details are listed in JIRA?
All the projects have some attributes that are displayed under the project summary section.
The list of attributes in JIRA is
- Nature of the project
- Keys for the project
What are the things that are not cloned from the original issue?
Things that aren’t cloned:
- Time tracking
- Issue History
- Links to Confluence pages
What is a Sub-task in JIRA?
Sub-task is the way of splitting up a parent issue into a number of smaller tasks that can be assigned and tracked separately. All the sub-tasks to a parent issue are summarised on the parent issue’s main screen. Sub-tasks always belong to the same project as their parent issue.
How is a sub-task created in JIRA?
Navigate to the issue you would like to be the parent issue of the sub-task you are about to create.
- Select More > Create Sub-Task. You will see the Create Subtask screen.
- Fill in the details as needed, and then click Create at the bottom of the page.
How to define a component in JIRA?
Components are sub-sections of a project. They are utilized to assemble issues within a project into smaller parts.
Managing a project’s components
- Sign in to JIRA as a project administrator.
- Choose Settings > Projects > and click the name of a project. The Project Summary page will appears.
- Choose Components in the left menu. The Components page is shown, demonstrating a rundown of Components and every Component’s information.
What are the Version control systems we can integrate with JIRA?
JIRA can be integrated with version control systems such as Git, Subversion, Visual SourceSafe, etc.,
Explain how you can edit multiple issues at the same time?
Editing multiple issues at the same time can be done by performing a bulk operation. To perform this bulk operation, you will need the global Make bulk changes permission and the relevant permission for each project.
Bulk operations available in JIRA are as follows
- Transition multiple issues through a workflow
- Delete multiple issues
- Move multiple issues
- Edit multiple issues
- Watch or stop watching multiple issues