testing Online Quiz - 138

Configuration management should control all items that affect test execution and results reproducibility. Option A is correct because it includes: (1) the test object (system under test), (2) test material (test cases, test data, scripts), and (3) test environment (hardware, software, network). If any of these change without control, tests may produce different results. Option B misses the test object and environment. Option C incorrectly excludes test material from configuration control. Option D misses the critical test environment. Complete traceability requires controlling all three elements.

Automating test execution is challenging mainly because maintaining the test environment, scripts, and data over time is labor‑intensive. The other options cite tool learning effort or output recognition limits, which are less central to the difficulty.

The V-Model is a software development model that shows the relationship between each development phase and its associated testing phase. Option A is correct because the V-Model illustrates how test activities (unit, integration, system, acceptance) correspond to and integrate with development phases (requirements, specification, design, implementation). Option B is incorrect - the V-Model is highly relevant for testing. Option C is incorrect - there's no single 'official' ISTQB model. Option D describes a testing lifecycle but doesn't capture the V-Model's key feature: the mapping between development and verification phases.

Quality means conformance to requirements - the degree to which the software meets its specified requirements. Option C is correct and aligns with the classic definition from software engineering (Crosby, 1979). Options A and B are slogans, not definitions. Option D is incomplete - software may work as designed but if design doesn't meet requirements, it's not quality. 'Conformance to requirements' is the standard, objective definition used in software quality assurance because it provides a measurable criterion: does the system do what was specified?

To solve this question, the user needs to know about equivalence classes and boundary testing. Equivalence partitioning is a software testing technique that divides the input data of a software unit into different partitions of valid and invalid data. The purpose of this is to reduce the number of test cases needed to test the software while increasing the effectiveness of the tests. Boundary testing is a software testing technique that checks whether the input data to a software system is at its minimum or maximum limits.

In this question, the valid equivalence classes are numbers between 10000 and 99999 inclusive. The valid boundaries are 10000 and 99999.

Let's go through each option and see which inputs are a result of designing tests for only valid equivalence classes and valid boundaries:

A. 1000, 5000, 99999: Option A includes invalid equivalence classes and is not a result of designing tests for only valid equivalence classes.

B. 9999, 50000, 100000: Option B includes an invalid boundary (100000) and is not a result of designing tests for only valid boundaries.

C. 10000, 50000, 99999: Option C includes valid equivalence classes and valid boundaries. It includes the minimum and maximum values of the valid equivalence classes.

D. 10000, 99999: Option D includes valid boundaries but only one valid equivalence class. It does not include other valid equivalence classes between 10000 and 99999.

E. 9999, 10000, 50000, 99999, 10000: Option E includes invalid equivalence classes (9999 and 10000) and duplicate input (10000). It is not a result of designing tests for only valid equivalence classes and valid boundaries.

Therefore, the correct answer is:

The Answer is: C

Alpha testing is conducted before release and typically involves a limited set of end‑user representatives working at the developer’s site. This matches the definition of pre‑release testing by end users at the developer’s location, making the selected option correct.

V21 is the billing system module where RHP (likely Residential Handset Process/Program) billing is processed. CASH, SGI, and None of the Above are incorrect locations for this specific billing function.

HUP stands for Hardware Upgrade Program, which is a common telecom industry program that allows customers to upgrade their handsets at subsidized rates. The other options (Handset Upgrade Payment, Handset Upgrade Process, Hardware Usage Payment) are not the standard expansion.

In V21, payments can be viewed by navigating through Bills->Payments menu path. This is the standard location for viewing payment history and details. The other options (Actions->Credit Evaluation, Page Options->Payments, Actions->One time payment) lead to different functions.

In V21, actual payment transactions are processed through Actions->One time payment menu. This is different from viewing payments (which is under Bills). Bills->Payments is for viewing payment history, not making payments.

CSM (Customer Service Management) is the V21 module that provides customer care services. It handles customer service requests and interactions. Priceplan, Number Management, and MPS are different modules for other functions (pricing, phone number management, and some other service).

Internet is the product not available in V21. LD (Long Distance), Messaging, and Second Line are products that are typically available. The question asks which is NOT available, making Internet (D) the correct answer.

A BAN (Billing Account Number) cannot be cancelled if it has active subscribers. All active subscribers must be moved or cancelled first before the BAN itself can be cancelled. This is a standard business rule to prevent account disruption.

LHO stands for Loyalty Handset Order, which is an order type for customers eligible for loyalty handset upgrades. The other options (Loyalty Hardware Order, Local Handset Order, Lost Hardware order) are not the correct expansion.

The current bill cycle is NOT changed when the company code is changed. The company code and bill cycle are separate attributes - changing one does not automatically change the other. This is a common misconception in billing systems.

CSM (Customer Service Management) applications are handled by CSR (Customer Service Representative). CSRs are the staff who process customer service requests through the CSM system. Customers and IT Support do not directly handle CSM applications in the same way.

Special Non Revenue is the BAN Type and Subtype combination that does not exist. Special Hardware, Business Prepaid, and Government Municipal are valid BAN type/subtype combinations. Non-revenue accounts typically have different classifications.

Activities on a BAN (Billing Account Number) in the V21 telecom billing system are logged and can be reviewed in the Memo section, which serves as an activity trail for audit and tracking purposes. The Equipment Window, BAN profile, and Subscriber Profile tabs display different types of information but not the activity log.

V21 billing system supports multiple payment methods: MACC (Multiple Account Credit Card) for credit card payments, PAC (Pre-authorized Collection) for automatic bank deductions, and Invoice for traditional billing. 'All the above' correctly captures all available payment options.

Credit evaluation is a mandatory pre-requisite before adding a new subscriber to a Billing Account Number (BAN) in telecom systems. This process assesses the customer's creditworthiness to determine appropriate credit limits and payment terms. Payments (A) and plan selection (C) happen after credit approval.