Top QA Concepts Interview Questions
Q – 1 Explain insurance project modules,and what we need to test on which functionality?
Ans- There are 4 core modules in any Insurance application .
1.underwriting
2.claims
3.accounts
4.reinsurance
Q – 2 Tell me In which of the software testing phase is QA involved & QC not involved?
Ans- QA is quality assurance and QC is quality control. The first one is preventive action later is detective. So QA is generally involves in assuring that no detect goes in product.
QA compromises of
1.Static Code anaysis
2.Reviews(Formal and informal)
While QC comprises of
1.Dynamic Code anaysis
2.Testing(Unit/Integration/System)
3.UAT
Q – 3 What is Context Driven Testing in Agile Method?
Ans- Context-driven testing is a paradigm for developing and debugging computer software that takes into account the ways in which the programs will be used or are expected to be used in the real world. In order to successfully conduct this type of testing, software developers must identify the intended market and evaluate the environments in which people are likely to employ the product.
Context-driven testing is sometimes considered a “flavor” of agile software development.
A program that works well for one person in a given situation might prove inadequate or inappropriate for another person or situation. For example, a word processor with mathematical symbols and a set of tools for positioning and manipulating them might be ideal for a college professor writing a physics textbook but cumbersome and annoying for a novelist.
Conversely, a simple text editor may be preferred by the novelist but be rejected by the professor. Context-driven testing revolves around the fact that there is no single “best solution” that applies to all cases. In addition, it takes into account the fact that complex software projects often evolve in unpredictable ways.
Context-driven testing is based on the notion that a computer program should be treated as a solution. It follows that if a program does not resolve the problem or situation it is meant to address, then it cannot be considered a success.
Advantages of context-driven testing include enhanced user-friendliness of the end product, optimized functionality for intended users and adaptability of the product to changing markets and social values. The context-driven methodology does not necessarily work well in all situations.
Other approaches might prove better for developers who are under the direct supervision and control of an autocratic “boss” who takes responsibility for the results of work done. Context-driven testing would likely prove superfluous in stable environments where conditions rarely or never change.
Q – 4 How to write the test cases for history of chat?
Ans- in settings there will be option like record chat click on record chat and chat with somebody the chat should be recorded that is after some days when you click on chat history it should be visible (the chat data) change to don’t record chat when you chat with somebody the chat should not be recorded
Q – 5 What is Change Request?
Ans- This is a Change Control mechanism for managing changing changes/enhancements outside the scope of a particular project or release you are working on.
E.g I’m working on project A, with requirements H,K,L,P. These are all the requirements we budgeted for for this realese anything outside of it is scope screep and thus will require a change request for it to be included at a later stage and properly managed and tracked.
Q – 6 Explain Agile Development Processes?
Ans- Agile software development is a conceptual framework for software engineering that promotes development iterations throughout the life-cycle of the project.
There are many agile development methods; most minimize risk by developing software in short amounts of time. Software developed during one unit of time is referred to as an iteration, which may last from one to four weeks. Each iteration is an entire software project: including planning, requirements analysis, design, coding, testing, and documentation.
An iteration may not add enough functionality to warrant releasing the product to market but the goal is to have an available release (without bugs) at the end of each iteration. At the end of each iteration, the team re-evaluates project priorities.
Q – 7 What is the difference between test case and test data?
Ans- Test Data:
collection of test input values that are consumed during the execution of a test, and expected results referenced for comparative purposes. Test data may be any kind of input to application, any kind of file that is loaded by the application or entries read from the database tables. It may be in any format like xml test data, system test data, SQL test data or stress test data.
Test Case :
A set of test inputs, execution conditions, and expected results developed for a particular objective, such as to exercise a particular program … Test cases is a sequence of steps to test the correct behavior of a functionality/feature of an application
Q – 8 What is Agile Development Processes?
Ans- Please refer to the below link:
http://en.wikipedia.org/wiki/Agile_software_development
Q – 9 What is the difference between web, window, desktop and client server application testing?
Ans- web is n-tier application
eg::
banking
window/desktop is on1-tier application
eg::
like paint application
client server is 2-tier application
eg::
appication with its own database
Q – 10 How to know that we have to use which tool for this project?
Ans- Tools are decided by Management i.e., the company you work for. since some tools require budge. Some tools can be downloaded from online and free to use.
Depends on the Project – if the project has any future releases – a test management tool is necessary and for the regression purposes, an automated tool is necessary to execute regression scripts.
If the project is used by a large number of users, to know the performance of the designed application a performance test tool is necessary.