software testing genius

ISTQB Agile Tester Extension Exam Theory Study Material Part 9

Welcome to “Software Testing Genius”. Subscribe to my RSS feed for latest content on Software Testing.

ISTQB Agile Tester Extension Exam Theory Study Material Part 9

Have a deep study of this entire question bank containing theory portion with detailed explanation. This study resource is as per the latest syllabus.

Just 1 hr. of time spent in brushing up your knowledge just before the ISTQB Agile Tester Extension Exam shall be of great help in clearing it.

Set of 10 Questions (Q. 81 to 90) with detailed explanation

Q. 81: What are the reasons for excessive code churn?

Few reasons for increased code churn are as under;

1) Ambiguous Requirements:
When the specs are incomplete or poorly written, the developers make wrong assumptions leading to higher code churn and as a result, they spend their time on something which is unbuildable.

2) Indecisive Stakeholder:
A product owner with a wavering mind can confuse the developer, with poor progress on the project. This can lower the morale of the team and can frustrate the developer.

3) Complex Problem:
Sometimes a complex problem can also lead to code churn rate going in the range of 60-80%. The developer must get cautioned if the

problem prolongs too much.

4) Coding New Features:
When a developer is working on a new feature, it is quite usual to expect a higher code churn. Developer tries to look for many implementation paths before finding the right solution. Hence code churn rates in the 60-80% range are quite normal when lots of exploratory coding is done.

5) Fine Tuning:
During the final stages before and after a release, troubleshooting small problems or changes result into higher code churn. The changes could be due to the code review.

6) Under-engagement:
When an engineer has high churn but low throughput, this could also be a sign of burnout. If they’re under-challenged, bored, or working on something they don’t really love, they could be at risk of getting poached by your team.

<<<<<< =================== >>>>>>

Q. 82: In addition to test automation, which testing related tasks can be automated?

By automating the following tasks agile teams can reduce the overhead costs. The team can thus spend time in developing and testing of new features.

1) Test data generation

2) Loading test data into systems

3) Deployment of builds into the test environments

4) Restoration of a test environment to a baseline (e.g., the database or website data files)

5) Comparison of data outputs

<<<<<< =================== >>>>>>

Q. 83: What skills a Tester in an Agile team should have?

Agile testers should have skills like;

1) Should be competent in test automation, test-driven development, acceptance test-driven development, white-box, black-box, and experience-based testing.

2) Should have good interpersonal skills.

3) Should be positive and solution-oriented with team members and stakeholders.

4) Should display critical, quality-oriented, skeptical thinking about the product.

5) Should actively acquire information from stakeholders (rather than relying entirely on written specifications).

6) Should accurately evaluate and report test results, test progress, and product quality.

7) Should work effectively to define testable user stories, especially acceptance criteria, with customer representatives and stakeholders.

8) Should collaborate within the team, working in pairs with programmers and other team members.

9) Should respond to change quickly, including changing, adding, or improving test cases.

10) Should plan and organize his/her own work.

<<<<<< =================== >>>>>>

Q. 84: What role a Tester plays in the Agile team?

The role of a tester in an Agile team includes;

1) Performing activities which generate and provide feedback
a) On test status,
b) On test progress,
c) on product quality,
d) On process quality.

2) Understanding, implementing and updating the test strategy

3) Measuring and reporting test coverage across all applicable coverage dimensions

4) Ensuring proper use of testing tools

5) Configuring, using, and managing test environments and test data

6) Reporting defects and working with the team to resolve them

7) Coaching other team members in relevant aspects of testing

8) Ensuring the appropriate testing tasks are scheduled during release and iteration planning

9) Actively collaborating with developers and business stakeholders to clarify requirements, especially in terms of testability, consistency, and completeness

10) Participating proactively in team retrospectives, suggesting and implementing improvements

<<<<<< =================== >>>>>>

Q. 85: What are the test-related risks faced by Agile organizations?

1) Testers work so closely with developers that they lose the appropriate mindset of a tester.

2) Testers become silent about inefficient, ineffective, or low-quality practices within the team.

3) Testers cannot keep pace with the incoming changes in time-constrained iterations.

<<<<<< =================== >>>>>>

Q. 86: What testing practices are followed in Agile Projects?

1) Writing tests in advance to express proper behavior.

2) Focusing on early defect prevention, detection, and removal.

3) Ensuring that the right test types are run at the right time and as part of the right test level.

These testing practices are followed both in Agile projects as well as traditional software development projects throughout the lifecycle.

<<<<<< =================== >>>>>>

Q. 87: What are the techniques used by the Agile teams for testing across the various test levels?

1) Test-driven development.

2) Acceptance test-driven development.

3) Behavior-driven development.

With these techniques the teams can get the benefit of early testing and QA activities, because the tests are defined before the code is written.

<<<<<< =================== >>>>>>

Q. 88: What is Test-driven development (TDD)?

Test-driven development is used to develop code guided by automated test cases.

# In TDD the tests are written at unit level and are code-focused.

# In TDD tests may also be written at the integration or system levels.

# TDD became popular through Extreme Programming.

# TDD is used in other Agile methodologies and in sequential lifecycles also.

# It helps developers focus on clearly-defined expected results.

# In TDD the tests are automated and are used in continuous integration.

<<<<<< =================== >>>>>>

Q. 89: What is the process of test-driven development?

The objective of test-driven development is “Red, Green, and Refactor.”
ISTQB Certification

1) Red: Create a test and make it fail.

2) Green: Execute the test in a tight loop until the test passes by any means necessary.

3) Refactor: Change the code to remove duplication in your project and to improve the design while ensuring that all tests still pass.

The Red / Green / Refactor cycle is repeated very quickly for each new unit of code.

<<<<<< =================== >>>>>>

Q. 90: What are the benefits of Test Driven Development

1) The suite of unit tests provides constant feedback that each component is still working.

2) The unit tests act as documentation that cannot go out-of-date, unlike separate documentation, which can and frequently does.

3) When the test passes and the production code is refactored to remove duplication, it is clear that the code is finished, and the developer can move on to a new test.

4) Test-driven development forces critical analysis and design because the developer cannot create the production code without truly understanding what the desired result should be and how to test it.

5) The software tends to be better designed, that is, loosely coupled and easily maintainable, because the developer is free to make design decisions and refactor at any time with confidence that the software is still working. This confidence is gained by running the tests. The need for a design pattern may emerge, and the code can be changed at that time.

6) The test suite acts as a regression safety net on bugs: If a bug is found, the developer should create a test to reveal the bug and then modify the production code so that the bug goes away and all other tests still pass. On each successive test run, all previous bug fixes are verified.

ISTQB Agile Tester Extension Exam Theory Study Material Part 10

Full Study Material on ISTQB Agile Tester Extension Exam 

Largest Database of Sample Papers - 1000+ Unique Questions for ISTQB Foundation Exam

ISTQB Foundation Exam - Full Crash Course for Download

ISTQB Advanced CTAL Test Analysts Exam - Full Crash Course for Download


ISTQB Advanced CTAL Test Manager Exam - Full Crash Course for Download


Consolidated Study Material - All ISTQB Certification Exams

What Successful Testers say about the Quality of this website

If you want to keep track of further articles on Software Testing,
I suggest you to subscribe my
RSS feed

.

You can also Subscribe by E-mail
and get All New articles delivered directly to your Inbox.


Quick Navigation of Software Testing Genius

Get your Absolutely Free Copy of Several MS PowerPoint Presentations & E-Books related to ISTQB, HP Load Runner, IBM RFT, HP QTP & QC Certification Exams, prepared by Popular Writers & Trainers, by writing to: Software.testing.genius@gmail.com

Full Study Material for Certification Exams on Automation Tools :

Study Material - IBM RFT Certification Exam

Study Material - HP QTP & QC Certification Exams

Study Material - HP LoadRunner Certification Exams for All Modules

Most Popular Topics in Demand:

Practical Roadmap to QTP Certification

Practical Roadmap to CSTE Certification

Consolidated Study Material - Testing & QA

Rehearsal of QTP in 1 Hr. -  Interview Questions

 

Comments :

0 comments ↓


Leave Your Comments: (*) Marked Fields are Mandatory

You can apply basic formatting to the text

Name *
 
Email Address *
 
Website
 
Speak your mind
characters
sex hikayeleri