Software Testing

Simple scenario where I have experienced testing schedule affected by environment change. I was working on a datawarehouse product, where a Multidimensional (MDD) cube building is possible, which was successful while executing on 2003 Windows server but the same was failing when tried to build the same over 2008 Windows server, later identified as an environment issue with 2008 windows server. Which requires fix from the Microsoft, thereby the testing schedule got affected.

How will you allocate resources in the following scenario: 1) You have 5 resources, 2 are well experienced (5+ years exp), 2 are experienced ( 3 + years) and 1 fresher. 2) 2 machines to conducted testing

The software testing life cycle (STLC) identifies all testing activities and their relationship with other activities in the software development life cycle (SDLC). Software testing should begin with the start of the software development life cycle. The main activities of any software testing life cycle (various phases involved in testing) are: 1. Requirements analysis 2. Test planning, including test strategy 3. Test development and review 4. Test environment setup and maintenance (including test data preparation) 5. Test execution (static and dynamic) 6. Test reporting 7. Test result analysis (see "Software bug life cycle" on this website for details) 8. Defect retesting 9. Test automation 10. Test maintenance 11. Regression testing 12. Test closure # QA activities that have an influence on the software testing life cycle: Software configuration management (change control) # All QA defect prevention activities Software testing activities and

Let us firstly understand as to what is a bug hunter? A bug hunter is an experienced & enthusiastic exploratory tester. Good bug hunters usually do the following: 1) Do initial exploratory testing of a suspect area, to develop ideas for more detailed attacks that can be performed by less experienced testers. 2) Explore an area that is allegedly low risk - can he quickly find bugs that would lead to reassessment of the risk? 3) Troubleshoot key areas that seem prone to irreproducible bugs. 4) Find critical bugs that will convince the project manager to slip a (premature) release date. How to prioritize the bug hunting activities? Generally the mission of a good bug hunter is finding bugs that are important (as opposed to insignificant) and finding them quickly. If so, what does this mean in terms of the tests that are run? You can use following suggestions to prioritize bug hunting in your software testing effort. 1) Test things that are changed before things that are the same. Fixe

Materialized views are disk based and update periodically base upon the query definition. Views are virtual only and run the query definition each time they are accessed.

A View created by a single table, can be updated and the updates made on a view will be reflected on the the base table. An updatable view lets you insert, update, and delete rows in the view and propagate the changes to the target master table. In order to be updatable, a view cannot contain any of the following constructs: SET or DISTINCT operators, an aggregate or analytic function, a GROUP BY, ORDER BY, CONNECT BY, or START WITH clause, a subquery (or collection expression) in a SELECT list or finally (with some exceptions) a JOIN . Views that are not updatable can be modified using an INSTEAD OF trigger.

Why are we doing ETL process: Customers are increasingly focusing on the collection and organization of data for strategic decision-making. The ability to review historical trends and monitor near real-time operational data has become a key competitive advantage. General goals of testing an ETL application: * Data completeness: Ensures that all expected data is loaded. * Data transformation: Ensures that all data is transformed correctly according to business rules and/or design specifications. * Data quality: Ensures that the ETL application correctly rejects, substitutes default values, corrects or ignores and reports invalid data. * Performance and scalability: Ensures that data loads and queries perform within expected time frames and that the technical architecture is scalable. * Integration testing: Ensures that the ETL process functions well with other upstream and downstream processes. * User-acceptance testing: Ensures the solution meets users' current expec

What is: The client–server characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services. Advantages: * In most cases, a client–server architecture enables the roles and responsibilities of a computing system to be distributed among several independent computers that are known to each other only through a network. This creates an additional advantage to this architecture: greater ease of maintenance. For example, it is possible to replace, repair, upgrade, or even relocate a server while its clients remain both unaware and unaffected by that change. * All data is stored on the servers, which generally have far greater security controls than most clients. Servers can better control access and resources, to guarantee that only those clients with the appropriate permissions may access and change data. * Since data storage is centralized, update