Dev Best Practices and Jira

Which field in Jira holds the type of issue?

• a) Project

• b) Issue Type

• c) Acceptance Criteria

• d) Summary

Which field in Jira is used to assign the issue to a specific user or team?

• a) Project

• b) Issue Type

• c) Assignee

• d) Priority

Which field in Jira represents a large body of work that can be broken down into smaller issues?

• Project

• IssueType

• Epic

• Summary

Which field in Jira is used to add additional details and context to an issue?

• Project

• Issue Type

• Description

• Summary

Which of the options describes the acceptance criteria best?

• a) Conditions of satisfaction for user stories.

• b) Brief description of the issue. issue.

• c) Type of issue in Jira.

• d) Priority of the issue.

Which of the following is considered a good practice for variable naming in coding?

• Using single-letter variable names to save space

• Naming variables based on their current value

• Using descriptive and meaningful names for variables

• Using reserved keywords as variable names

Which of the following is an important principle of code reuse and maintenance?

• Duplicating code to ensure independence

• Avoiding the use of functions or methods

• Never modifying code once it is written

• Encapsulating reusable code into functions or classes

Which of the following is a good practice for error handling in coding?

• Ignoring errors and letting the program continue execution

• Using generic error messages without providing specific details

• Handling errors gracefully by displaying meaningful error messages and taking appropriate actions

• Avoiding error handling altogether and relying on the user to fix issues

Which of the following is a good practice for writing functions or methods?

• Creating functions with a very large number of parameters

• Keeping functions concise and focused on a single task

• Writing functions that perform multiple unrelated tasks

• Avoiding the use of parameters in functions

Which of the following is a good practice for code version control?

• Making direct changes to the production code without tracking modifications

• Using a version control system to track changes and collaborate with other developers

• Storing code in a single, monolithic file to avoid version control complexities

• Avoiding the use of branching and merging in version control