1. Explain how Scripts are run in Groovy?
Scripts in Groovy are executed in the Java Virtual Machine (JVM) environment. You write the Groovy script, optionally compile it for performance, and then run it using the "groovy" command-line tool or within a Java application. The JVM interprets the Groovy code, allowing seamless integration with Java classes and libraries.
2. Explain what is Groovy?
Groovy is a dynamic and object-oriented scripting language designed to run on the Java Virtual Machine (JVM). It fully integrates with Java, offering dynamic typing, closures, and support for Domain-Specific Languages (DSLs). Groovy enables seamless interoperability with Java code, making it productive and expressive for developers while leveraging Java's extensive ecosystem.
3. Explain What Is Expandometaclass In Groovy?
Ans: ExpandoMetaClass is used to add methods, properties, static methods and constructors. Expandoclass does not inherited by default; you have to call ExpandoMetaClass.enable globally()
4. Explore the steps to create a Clone Issue?
Ans: Open the JIRA issue that wants to be cloned. Select More > Clone. Also can edit the Summary of the clone issue, if required. In case, the issue contains links to another issue (s): Select > In new clone issue as if or not to include the links. In case, the issue contains sub-tasks: Select > In new clone issue as if or not to create the sub-tasks. In case, the issue contains attachments: Select > In new clone issue as if or not to include the attachments. Click on the Create button.
5. What is Closure in Groovy?
In Groovy, a Closure is a block of code that can be assigned to a variable or passed as an argument to methods. It provides powerful functional programming capabilities and helps create concise and expressive code.
6. How a service desk works in JIRA
Your client presents a demand for your service agents through an entryway or by means of email. A service desk sees the demand in their Jira Service Desk line and investigates the issue. Your client and different members utilize the entry or email to talk about the demand with your service desk agent, who works in the Jira Service Desk. Your specialist finishes the demand and your client is fulfilled!
7. Explain the various stages of a defect in Jira/Qtest in your project?
The stages of a defect are: New/Open, Assigned, In Progress, Fixed/Resolved, Ready for Testing, Retest, Closed, Reopen (if needed), and Rejected (if applicable).
8. Explore the steps to create a Clone Issue?
To create a Clone Issue in Jira, open the issue, click "More," select "Clone," configure the details, choose the destination project and issue type, and click "Create."
9. What is the purpose of the JIRA dashboard?
The Jira dashboard provides users with a personalized and centralized view of project information, real-time insights, customization options, quick navigation, transparency, and monitoring key performance indicators (KPIs).
10. Explain Cloning an Issue in JIRA?
Cloning, or copying, an issue that allows you to rapidly making a copy of an issue inside a similar project. The clone issue is a mirror image of the original issue, containing similar data put away in the original issue — e.g. Summary, Affects Versions, Components, and so on. The clone issue can likewise be connected to the original issue. A clone issue is a different element from the original issue. Tasks on the first issue have no impact on the clone issue and the other way around. The main connection is a link – if made – between the original issue and the clone issue. Cloning an Issue retains: Summary Description Assignee Environment Reporter Components Affects Versions Fix For Versions Priority Issue Type Security Attachments Issue Links Project Here are the issues that are cannot be cloned: Time tracking Issue history Comments and Links to Confluence pages
11.Mention one similarity and one difference between JIRA Scrum and JIRA Kanban.
Similarity: Both JIRA Scrum and Kanban is considered as the most powerful process tool for optimization of work and the processes as both processes focus is on continuous optimization and visualizing the workflow. In these cases, large and the complex tasks are broken down and each individual tasks are worked on and completed efficiently. Difference: Scrum board is the work mode where progress of sprints and tracking of its work is done. Here the team determines the list of issues that has become backlog and then these issues are moved to sprints as per team plan. In the case of the Kanban board, the work in progress activities is being maintained and their process flow is tracked. Here the team decides the increase and decrease of the number of issues that is to be displayed in each status of the workflow.
12.What are burndown and burn-up charts in agile methodology?
Burndown Chart: Tracks remaining work over time in a sprint.
Burn-up Chart: Displays completed work over time in a sprint.
13.What are the major Agile components?
User Stories: Descriptions of desired functionality.
Sprints/Iterations: Fixed timeframes for development.
Daily Stand-up Meetings: Short daily progress updates.
Sprint Planning: Defining work for each sprint.
Sprint Review: Demo and feedback at sprint end.
Sprint Retrospective: Team improvement discussion.
Product Backlog: Prioritized list of requirements.
Agile Board: Visual representation of work flow.
14.Mention the challenges involved in developing Agile Software?
Changing Requirements: Adapting to evolving needs.
Short Iterations: Pressure to deliver quickly.
Distributed Teams: Communication challenges.
Lack of Experience: Difficulty in adopting Agile.
Stakeholder Involvement: Engaging stakeholders.
Scaling Agile: Adapting Agile to larger projects.
Technical Debt: Balancing speed with quality.
Balancing Individual and Team Goals: Collaboration vs. individual goals.
15.handle conflicts within an Agile team, especially when team members have different opinions
Active Listening: Encourage attentive listening.
Facilitated Discussions: Mediated discussions.
Consensus Building: Aim for agreement.
Emphasize Team Goals: Focus on project success.
Respect Diversity: Value diverse viewpoints.
Mediation: Use neutral third party if needed.
Set Clear Expectations: Establish conflict resolution norms.
Continuous Improvement: Improve team dynamics through retrospectives.
