Answer:- Cubes are data processing units comprised of fact tables and dimensions from the data warehouse. They provide a multi-dimensional analysis. OLAP stands for ‘Online Analytics Processing,’ and OLAP Cubes store voluminous data in a multi-dimensional form for reporting purposes. They consist of facts called ‘measures’ categorized by dimensions.

Answer:- Types of data warehouse applications are: • Info Processing • Analytical Processing • Data Mining Data mining can be defined as the process of extracting hidden predictive information from large databases and interpreting the data, while data warehousing may make use of a data mine for the analytical processing of the data in a faster way. Data warehousing is the process of aggregating data from multiple sources into one common repository.

Answer:- Software testing is a validation process which confirms that a system works as per the business requirements. It qualifies a system on various aspects such as usability, accuracy, completeness, efficiency, etc. ANSI/IEEE 1059 is the global standard that defines the basic principles of testing.

Answer:- The testing activity ends when the testing team completes the following milestones. • Test case execution The successful completion of a full test cycle after the final bug fix marks the end of the testing phase. • Testing deadline The end date of the validation stage also declares the closure of the validation if no critical or high-priority defects remain in the system. • Code Coverage(CC) ratio It is the amount of code concealed via automated tests. If the team achieves the intended level of code coverage (CC) ratio, then it can choose to end the validation. • Mean Time Between Failure (MTBF) rate Mean time between failure (MTBF) refers to the average amount of time that a device or product functions before failing. This unit of measurement includes only operational time between failures and does not include repair times, assuming the item is repaired and begins functioning again. MTBF figures are often used to project how likely a single unit is to fail within a certain period of time

Answer:- In software testing, verification is a process to confirm that product development is taking place as per the specifications and using the standard development procedures. The process comprises the following activities: • Inspections • Reviews • Walk-throughs • Demos

Answer:- Static testing is a white-box testing technique that directs developers to verify their code with the help of a checklist to find errors in it. Developers can start the static testing without actually finalizing the application or program. Static testing is more cost-effective than dynamic testing as it more areas than dynamic testing in a shorter time.

Answer:- It is a standard software testing approach that requires testers to assess the functionality of the software as per the business requirements. The software is treated as a black box and validated as per the end user’s point of view.

Answer:- A test plan stores all possible testing activities to ensure a quality product. It gathers data from the product description, requirement, and use case documents. The test plan document includes the following: • Testing objectives • Test scope • Testing the frame • Environment • Reason for testing • Criteria for entrance and exit • Deliverables • Risk factors

Answer:- Test coverage is a quality metric to represent the amount (in percentage) of testing completed for a product. It is relevant for both functional and non-functional testing activities. This metric is used to add missing test cases.

Answer:- It’s considered not possible to perform 100% testing of any product. But you can follow the below steps to come closer. • Set a hard limit on the following factors: o Percentage of test cases passed o Number of bugs found • Set a red flag if: o Test budget is depleted o Deadlines are breached • Set a green flag if: o The entire functionality gets covered in test cases o All critical and major bugs must have a ‘CLOSED’ status

Answer:- Unit testing has many names such as module testing or component testing. Many times, it is the developers who test individual units or modules to check if they are working correctly. Whereas, integration testing validates how well two or more units of software interact with each other. There are three ways to validate integration: • Big Bang approach • Top-down approach • Bottom-up approach

Answer:- No. System testing should start only if all modules are in place and they work correctly. However, it should be performed before UAT (user acceptance testing).

Answer:- Various types of Software Testing used by manual testers are as follows: • Unit testing • Integration testing • Regression testing • Shakeout testing • Smoke testing • Functional testing • Performance testing • o Load testing o Stress testing o Endurance testing • White-box and Black-box testing • Alpha and Beta testing • System testing

Answer:- The test driver is a section of code that calls a software component under test. It is useful in testing that follows the bottom-up approach. The test stub is a dummy program that integrates with an application to complete its functionality. It is relevant for testing that uses the top-down approach. For example: Let’s assume a scenario where we have to test the interface between Modules A and B. We have developed only Module A. Here, we can test Module A if we have the real Module B or a dummy module for it. In this case, we call Module B as the test stub. Now, Module B can’t send or receive data directly from Module A. In such a scenario, we’ve to move data from one module to another using some external features called test driver.