Testing General - 1

1. What types of documents would you need for QA, QC, and Testing?
brs and srs and use cases, test plan test cases.

2. What did you include in a test plan?
Test Plan is a big document that contains all the information about your project, objectives, scopes, roles and responsibilities, test-set(set of test cases), test -bed(types of testing, execution environment), test-strategy, schedules etc.

3. Describe any bug you remember.
Examples: Due to silk test tool does not support default synchronization concept, so the tool fails, since there is no time out option in tools menu. For eg follow these steps: 1.select 1st record in flight reservation form 2.perform some change in test record

3.Click update order 4.Open Help from the flight 5.run the script

4. What is the purpose of the testing?
The purpose of testing can be quality assurance, verification and validation, or reliability estimation. Testing can be used as a generic metric as well. Correctness testing and reliability testing are two major areas of testing. Software testing is a trade-off between budget, time.

5. What do you like (not like) in this job?
like: it’s very interesting, challenging by thinking about the application in the end user's perception. it is interesting that we are doing destructive work but in the long term it is a constructive work.

7. What is the difference between QA and testing?
QA is more interested in the Process whereas Testing is more interested in the Product. As rightly pointed out by some people, QA i.e. oriented towards prevention and testing is oriented towards detection.

8. How do you scope, organize, and execute a test project?
Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects.

9. What is the role of QA in a development project?
QA is responsible for the Preventive action. That's QA is necessary right from the requirement gathering phase. QA engineer needs to set a goal for each and every stage of the project life cycle and make sure the development team achieves the plan. If not conduct casual analysis meeting to find out problem and eradicate in the upcoming phases

10. What is the role of QA in a company that produces software?
Quality assurance personnel are responsible for validating project assumptions and ensuring the quality of phase deliverables. Quality assurance personnel should be independent of the development process

11.Define Quality

For me as you understand it quality is a process to satisfy the given requirement and delivered on time, cost effective and its maintainable

12. Describe to me the difference between validation and verification.
Verification takes place before validation, and not vice versa. Verification evaluates documents, plans, code, requirements and specifications. Validation evaluates the product itself. The input of verification is the actual testing of an actual product. The o/p of verification is nearly perfect set of documents, plans, specifications and requirements

13. Describe to me what you see as a process. Not a particular process, just the basics of having a process.
The sequence of activities, people, and systems involved in carrying out some business or achieving some desired result

14. Describe to me when you would consider employing a failure mode and effect analysis.
FMEA (Failure Mode and Effects Analysis) is a proactive tool, technique and quality method that enables the identification and prevention of process or product errors before they occur. Failure modes and effects analysis (FMEA) is a disciplined approach used to identify possible failures of a product or service and then determine the frequency and impact of the failure

15. What are the properties of a good requirement?
Very clear, complete, attainable, cohesive, testable

16. How do you differentiate the roles of Quality Assurance Manager and Project Manager?
Their duties are different. The QA manager is a part of the project in which he is responsible for the quality of the intended project where as the project manager is responsible for the whole project and he coordinates all the departments in making project

17. How do you deal with environments that are hostile to quality change efforts?
It depends on the end user or client. if he is computer literate, then it's better to provide clear documentation on each and every feature and actions. if he is not computer literate, then reengineering(start from the scratch) is better.

18. In general, how do you see automation fitting into the overall process of testing?
For this first we have to see the drawbacks of Manual testing. 1.More no. of people required. 2. More time is consumed. 3. it's a tedious task. 4.We can't repeat the test easily 5. Concurrency is missing Automation

19.How do you promote the concept of phase containment and defect prevention?

Phase Containment (prevention of spread of something harmful): Suppose we find a defect at design stage. so we prevent that to spreading to the next stage. i.e. we traced back that defect and correct that in requirements and then in design. After that only you can go to next phase.

Defective Prevention: QA people try to prevent defects by monitoring the whole development process

20. What kinds of testing have you done?
I handled functionality testing, GUI Testing, Database testing, Regression Testing. Also involved in Smoke testing once a build is released from the development team.

21. Have you ever created a test plan?
Test plan is nothing but the events, which drives the testing activities; test leads handle this job.

22. Have you ever written test cases or did you just execute those written by others?
Primary responsibility of the tester is to write the test cases. Writing test cases and executing his own test cases gives best result in testing. After studying the functional and technical documents I prepare test cases and test the application basing on the test cases written

23. What did your base your test cases?
My test cases mainly base on the CRS (Customer requirement specifications)& SRS (System requirement specifications), The CRS should include all functional & non-functional requirement specifications.

24. How do you determine what to test?
Study the Requirements document, design document thoroughly, to understand the main functionality of the application. After u gets a clear idea on that then only start write test cases. if u have any doubts send them to the concerned person(Generally by Test lead or Business Analyst)

25. How do you test if you have minimal or no documentation about the product?
In this situation I will try to test the application with the perception of end user. And i use my (or someone’s) previous experiences. Here we are not preparing any formal test plans and testcase documents. Most of the time we perform adhoc testing on this application

26. Describe me to the basic elements you put in a defect report?
The bugs are entered into a bug-reporting tool. Nowadays, every organization uses the Test Director as their Test Management Tool. This has Defects section, where you can follow the Steps after Clicking Add Defect Button

27. How do you perform regression testing?
Regression Testing is carried out both manually and automation. The automatic tools are mainly used for the Regression Testing as this is mainly focused repeatedly testing the same application for the changes in the design etc. It involves executing test case with defects until they are removed completely.

28. At what stage of the life cycle does testing begin in your opinion?
Testing starts right from the requirements

29.How do you analyze your test results? What metrics do you try to provide?
Test results are analyzed to identify the major causes of defect and which is the phase that has introduced most of the defects. This can be achieved through cause/effect analysis or Pareto analysis. Analysis of test results can provide several test metrics like Defect Density, Test effectiveness, DRE

30. Where do you get your expected results?
We get expected results from the SRS and Functional Design Documents. If there is no clear documentation we prepared expected results from 1. Previous similar products. 2. by communicating with the developers 3. by common sense