QA Testing

1.What is Software Testing?

A. Testing involves operation of a system or application under controlled conditions and evaluating the results, the controlled conditions should include both normal and abnormal conditions.Testing is a process of executing a program with the intend of finding the errors.

2. What is the Purpose of Testing?

A. The purpose of testing is

1· to uncover hidden errors

2· to achieve the maximum usability of the system

3· to Demonstrate expected performance of the system

3. What types of testing do testers perform?

A. Two types of testing 1.Functional testing 2. Non functional testing.

4. What is the Outcome of Testing?

A. The outcome of testing will be a stable application which meets the customer Req's

.5. What kind of testing have you done?

A. Usability, Functionality, System testing, regression testing, and AUT (it depends on the person).

6. What is the need for testing?

A. The Primary need is to match requirements get satisfied with the functionality

7. What are the entry criteria for Functionality and Performance testing?

A. Entry criteria for Functionality testing is Functional Specification /BRS (CRS)/User Manual. An integrated application, Stable for testing.Entry criteria for Performance testing is successfully of functional testing, once all the requirements related to functional are covered and tested, and approved or validated

8. Why do you go for White box testing, when Black box testing is available?

A. A benchmark that certifies Commercial (Business) aspects and also functional (technical) aspects is objectives of black box testing. Here loops, structures, arrays, conditions, files, etc are very micro level but they arc Basement for any application, So White box takes these things in Macro level and test these thingsEven though Black box testing is available, we should go for White box testing also, to check the correctness of code and for integrating the modules.

9. What are the entry criteria for Automation testing?

A. Application should be stable. Clear Design and Flow of the application is needed.

10. What is testing?
A. “The execution of an application manually with intention of finding errors.

11. When to start and Stop Testing?

A. This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are: Deadlines (release deadlines, testing deadlines, etc.) Test cases completed with certain percentage passed Test budget depleted Coverage of code/functionality/requirements reaches a specified point Bug rate falls below a certain level Beta or alpha testing period ends

12.What is Quality?

A. It ensures that software is a Bug free, delivered in time, with in budget, meets customer requirements and maintainable. Quality standards are different in various areas like accounting department might define quality in terms of Profit.

13. What is Baseline document?

A. The review and approved document is called as baseline document (i.e.) Test plan, SRS

14. What is verification?

A. To check whether we are developing the right product according to the customerrequirements and company standards r not. It is a static process.

15. What is validation?

A. Validation is a process of evaluating system or components at end of the development process to determine whether it is satisfies specified req. r not. It is a Dynamic process.

16. What is quality assurance?

A. Quality Assurance measures the quality of processes used to create a quality product.1. It is a system of management activities.2. It is a preventive process.3. It applies for entire life cycle.4. Deals with Process.

17. What is quality control?

A. Quality control measures the quality of a product1. It is a specific part of the QA procedure.2. It is a corrective process.3. It applies for particular product.4. Deals with the product.

18. What is SDLC and TDLC?

A. Software development life cycle (SDLC) is life cycle of a project from starting to ending of the project.1. Requiremnts Specification. 2. Analysis3.Design 4.Coding5.Testing 6.Delivery & Maintenance.Software Test Life Cycle (STLC) is a life cycle of the testing process.1. Test Initiation. 2. Test Planning3. Test case Design. 4. Review 5.Test case Execution6. Bug Reporting. 7. Test Closer

19.What are the Qualities of a Tester?

A. Tester should have qualities like 1. Ability to break 2.paitence 3.communication 4. Presentation 5.team work. 6. Negative thinking with good judgment skills

20.What are the various levels of testing?

A. The various levels of testing like1· Unit level testing2. Module Level testing 3. Integration level Testing4. System level testing5· UAT Level Testing

21.What are the types of testing you know and you experienced?

A. I am experienced in Black Box testing.

22. After completing testing, what would you deliver to the client?

A. It is depend upon what you have specified in the test plan document.The contents delivers to the clients is nothing but Test Deliverables.1. Test plan document 2.Master test case document 3.Test summary Report.4. Defect Reports.

23. What is a Test Bed? & Harness?

A. List of test cases to be executed is test bed. Harness means ready to start testing. Test harness =Test bed + Test Environment (test bed= list of test cases. Test environment = S/W+H/W).

24. Why do you go for Test Bed?

A. We will prepare test bed bcoz first we need to identify under which environment (Hardware, software) the application will run smoothly, thenonly we can run the application smoothly without any intereptions.

25. What is Severity and Priority and who will decide what?

A. Severity and priority will be assigned for a particular bug to know the importance of the bug. Tester can decide the severity and priority.Severity: How severely the bug is effecting the application.Priority: Informing to the developer which bug to be fix first.

26. Can Automation testing replace manual testing? If it so, how?

A. Yes, it can be done manually when the project is small, having more time.We can test with minimum number of users.

27. What is a test case?

A. A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly.
(Or)
It is a perception of test engineer to validate a specific functionality is called test case. It is one of the out coming document, it is a unique condition. In the testing phase to validate functionality a test engineer can take a several real time scenarios both positive and negative.

28. What is a test condition?

A. The condition required to test a feature. (Pre condition) Test condition derived from requirement specifications. It includes all possible combinations and validations

29.What is the test script?

A. Test script is the script which is generated by an automation tool while recording an application features. It contains navigations steps, Instructions, data exp, result……. To execute the test case

30. What is the test data?

A. Test data means the input data (valid, invalid data) giving to check the feature of an application is working correctly.

31. What is an Inconsistent bug?

A. The bug which is occurring.The bug which can’t catch even if we follow a process. It may occur, May not occur when we follow same scenario

32. What is the difference between Re-testing and Regression testing?

A. Re-testing: Testing the already tested application in the given AUT. In order to check the reproduceble of defect and role out the environmental issues.
Regression testing: Testing the already tested functionalities in the given AUT. Whether the already tested functionalities are changed or remain same because of newly added functionality to the application.

33. What are the different types of testing techniques?

A. 1. BVA (Boundary Value Analysis) 2. ECP (Equalence class partitiency) 3. Error Guessing

34. What are the different types of test case techniques?

A. 1. Equilance Partition. 2. Boundary Value Analysis. 3. Error guessing.

35. Differentiate Test bed and Test Environment?

A. Both are same. But little bit difference is there test bed is nothing but list of test cases to excuted. Test environment means S/W+ H/W.

36. What ifs the difference between defect, error, bug, failure, fault?

A. Defect: Deviation from desired functionality (Detected by test engineer- accepted by developer.)
Error: Mistake in coding (Un desirable deviation from requirements)Bug: Missing functionality / wrong functionality / Extra un wanted functionality
Failure: Absence of expected result (Client side people can find the mistake)
Fault: A Problem, which causes the system not to perform its task.

37. What is the difference between quality and testing?

A. QA is more a preventive thing, ensuring quality in the company and therefore the product rather than just testing the product for software bugs?TESTING means "quality control"Quality control measures the quality of a product.Quality Assurance measures the quality of processes used to create a quality product.

38. What is the difference between White & Black Box Testing?

A. White Box Testing: Based on the knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions. Black Box testing: - Not based on any knowledge of internal design or code.Tests are based on requirements and functionality. (It is a build level testing, to validate the customer requirements and an expectation depends on external interface).

39. What is the difference between Quality Assurance and Quality Control?

A. Refer Question no.16 & 17Quality Assurance measures the quality of processes used to create a quality product.Quality control measures the quality of the product.

40. What is the difference between Testing and debugging?

A. The Purpose of testing is to show the program has bugs.The Purpose of debugging is find the error/ misconception that led to failure and implement program changes that correct the error.

41. What is the difference between bug and defect?

A. Defect: While executing the test case if u found any mismatch, that u will report it to the development team that is called defect. Deviation from desired functionality (Detected by test engineer- accepted by developer.)Bug: Missing functionality / wrong functionality

42. What is the difference between verification and validation?

A. Verification: To check whether we are developing the right product according to the customer requirements and company standards are not. It is a static process.
Validation: Validations is a process of evaluating system or components at end of the development process, to determine whether it is satisfies specified requirement r not. It is a Dynamic process.

43. What is the difference between unit testing and integration testing?

A. Unit Testing: It is a testing activity typically done by the developers not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code.Integration testing: testing of combined parts of an application to determine if they function together correctly. (Functionality flow of navigation) The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.

44. What is the diff between Volume & Load?

A. Combination of Load, volume and stress testing comes under performance testing.Load Testing: To test the performance of the application by gradually increasing the user loads.Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.Volume Testing: To test whether it can able to send max data according to client req's.

45. What is diff between Volume & Stress?

A. Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.Volume Testing: To test whether it can able to send max data according to client req's.

46. What is the diff between Stress & Load Testing?

A. Load Testing: To test the performance of the application by gradually increasing the user loads.Stress Testing: TO test the performance of the application and to find the server break down or where the server crashes.

47. What is the Diff between Two Tier & Three tier Architecture?

A. Two Tier Architecture: It is nothing but client server Architecture, where client will hit request directly to server and client will get response directly from server.Three tier Architecture: It is nothing but Web Based application, here in between client and server middle ware will be there, if client hits a request it will go to the middle ware and middle ware will send to server and vise-versa.

48. What is the diff between Integration & System Testing?

A. Integration testing: testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.System Testing: system testing will conducted on the entire system to check whether it is meeting the customer requirements r not. (Or)
Testing the application as a whole from login to logout, to covering by all requirements with functionality end to end, interms of Usability, Functionality, and Non-functionality is System testing.

49. What is the diff between walk through and inspection?

A. Walk through: A 'walk through' is an informal meeting for evaluation or informational purposes. Little or no preparation is usually requiredInspection: Inspection is an formal meeting, here every thing discussed will be documented such as a requirements spec or a test plan, and the purpose is to find problems and see what's missing, The result of the inspection meeting should be a written report.

50. What is the Diff between static and dynamic?

A. Static Testing: Test activities that are performed without running the software is called Static Testing, it includes inspections, walk throughs and desk checks.Dynamic testing: Test activities that are performed by running the software is called dynamic Testing.

51. What is the diff between alpha testing and beta testing?

A. Alpha Testing: Alpha testing will be performed by in the presence of client in our environment with dummy data, in this phase some major bugs can be allowed, later which will be solved by our development team.Beta testing: Beta testing will be performed by client in his environment with real data.

52. What is the diff between Client Server & Web Based Testing?

A. Client server application is 2 tier applications and web Application is n tier application.Client server is the single user application and the web Application is the multi User .

53. What is functional testing?

A. It is mandatory level in Block box testing, validating the functionality of the application according to business requirements, to check the behavior of the application. Functional testing main object is “To meet customer requirements”. It is also known as ‘Requirements testing’, test engineers validates the correctness of functionalities in terms below coverage’s.1. Whether it is taking valid text data or not.2. If it is taking valid data, it is giving correct output or not3. If we are giving invalid data whether it shows error messages or not4. It is preventing wrong (negative) navigations or not5. Impact of front operations on backend tables contents6. Order of functionalities.

54. What are the risks involved in the testing?

A. 1.Resource risk A. Human Risk B. H/W risks C. S/W risks 2. Technical Risks 3. Commercial RisksRisks involved in testing process 7 types……1. Lack of time2. Lack of knowledge3. Lack of resources4. Lack of documents5. Lack of communication6. Lack of seriousness7. Lack of deliverables.

55. What is mean by UAT?

A. If we perform every test as user acceptance test, after completion of all possible functional system tests, our organization management is concentrate on UAT. The main object is “Feed back from customer side people”. AT is done to achieve the following1. User specified requirements have been satisfied2. Functionality is doing as per supporting documents3. Expected performance have been achieved4. End user is comfortable to use the application
UAT 2 types
Alpha Testing: In the presence of client our environment is called alpha testing
Beta testing: In the presence client and his environment our people can do testing is called beta testing.

56. What is traceability matrix?
A. It is an inner mapping between requirement id to defect id via test case id. This is gives a summary report on that total testing process. It is a brief conclusion of testing process, quality can be measured by using trace matrix. Trace matrix has been maintained to ensure that verification & validation of the testing is complete.

57. What is SRS Documents contains? What’s its use?
A. It defines the complete behavior of the system to be build.
Bridge between customer and company.
1.INTRODUCTION
a .purpose
b.context diagrams
c.scope
d.functional de composition diagrams
e.definitions & acronyms
f.system functions
g.references & Major constraints

2.FUNCTIONAL REQUIREMENTS
a.database requirements
b.UI req
c.computability req
d.reports req

severity req
i
system features
j
traceability matrix

3
NON FUNCTIONAL REQ
4
COMMON CONSIDERATIONS
a
performance req
a
External interface specifications
b
safety req
b
user interfaces
c
security req
c
hardware interfaces
d
software quality attributes
d
software interfaces
e
business rules/other req
e
communication interfaces


58. What is the advantage of test case documents?
A. 1. Proper testing can be done.
2. We can validate the application in all possible permutation and combination.
3. Without repeating, without missing the tasks we can do the testing.
4. Any feature changes occur we can modify the test case document.
5. It makes us to follow a democratic approach
6. It useful for feature correspondence.
7. We can measure how many requirements covered.
8. At what level the quality is coming out.
9. The defect severities and prioritized in easy manner.
10. Correspondence will be developed to customer, tester, and developer also.

59. What is negative testing?
A. We test the application in all perspective. What is the application is not suppose to do. We give the invalid data for negative testing.

60. What is smoke and Sanity testing?
A. Smoke: Whenever we received the initial build from the developer we check whether all fields are available in every screen or not? And also we check the stability of the application.
Sanity: All fields are available ok but that fields are testable are not? Ex: Edit box is there editable or not. List box there list out all items or not?

61. What are the challenges you faced while you testing?
A. 1. Avoiding the duplication of testing effort across the different phases of testing
2. Reduce the cycle time of testing.
3. Standard testing process, templates and methodologies
4. Maintaining objectivity in the testing process
5. Availability of test environmental trained resources
6. Involvement testing in the entire system life cycle
7. Communication with development team
8. Unstable work package & environment
9. Shared Environment
10. Lack of dedicated environment support
11. Short time frames
12. Co-ordination with other team
13. Access from offshore for environment setup
14. Slow response
15. Knowledge acquisition due to various sub systems

62. What us usability testing?
A. Test execution process starts with usability testing. We are looking for the user friendliness of the application. This testing main object is “User friendliness”. A common user can use the application without any hesitation. Instructions should be available on every screen.
1. Ease of use: Understandable screens
2. Look & Feel: Attractiveness or pleasantness of screens
3. Speed in interface: Less number of events to complete a task
4. Context sensitiveness of user commands
5. Help documents.
6. Meta data (Tool tips).

63. What is BVA and ECP?
A. BVA: Identifying the boundary conditions of an object with in a given range of inputs.
ECP: Dividing the input domain in to valid and invalid types according to the business usage of the application.