Sei sulla pagina 1di 3

Software Testing FAQ 1) Difference between Quality Assurance and Quality Control?

QA:It is process oriented it involves in entire process of software development. Prevention oriented. QC: It is product oriented. work to examine the quality of the product. Detection oriented. 2) what is a bug? Mismatch in Software Application 3.what is a test case? Testcase is set of input values, execution preconditions,expected results and ex ecution post conditions, developed for a particular objective or test conditons, such as to exercise a paticular program path or to verify compliance with a spe cific requiremnt. 4) What is the purpose of test plan? Test plan document is prepared by the test lead or team lead,it contains the con tents like introduction,objectives,test strategy,scope,test items,program module s user procedures,features to be tested features not to tested approach,pass or fail criteria,testing process,test deliverables, testing, tasks, responsibilitie s,resources,schedule, environmental requirements, risks & contingencies,change m anagement procedures,plan approvals,etc all these things help a test manager und erstand the testing he should do & what he should follow for testing that particular project. 5) what is basis for testcase review? the main basis for the test case review is 1.testing techniques oriented review 2.requirements oriented review 3.defects oriented review. 6)what are the contents of SRS documents? System requirements specifications and Functional requirements specifications. 7)what is Regression testing? After the remaining Bug fixed connected Bug fixed ,testing the application whether the fixed bug is affecting functionality of the application or not.Majorly in regression testing module and it's modules are checked for thier integrity after bug fixation.

8) what is build duration? it is a tine gap between old version build and new version build in new version

build some new extra features are added 9) What is test deliverables? Test deliverables are nothing but documents preparing during testing like test p lan document test case docs bug reports etc.. Test deliverables will be delivered to the client not only for the completed ac tivities ,but also for the activities, which we are implementing for the better productivity.(As per the company's standards) 1.QA Test Plan 2.Test case Docs 3.QA Test plan, if we are using Automation. 4.Automation scripts 5.QA Coverage Matrix and defect matrix. 6.Traceability Matrix 7.Test Results doc 8.QA Schedule doc(describes the deadlines) 9.Test Report or Project Closure Report.(Prepared once we rolled out the project to client) 10.Weekly status report(sent by PM to the client) 11.Release Notes. 10) If a project is long term project , requirements are also changes then test plan will change or not? why? Yes..definitely. If requirements change, the design documents, specifications (f or that particualr module which implements the requiremnts) will also change. He nce the test plan would also need to be updated. 1) What is Database testing? Database testing basically include the following. 1)Data validity testing. 2)Data Integrity testing 3)Performance related to database. 4)Testing of Procedure, triggers and functions. for doing data validity testing you should be good in SQL queries For data integrity testing you should know about referential integrity and diffe rent constraint. For performance related things you should have idea about the table structure an d design. For testing Procedure triggers and functions you should be able to und erstand the same. 2) What we normally check for in the Database Testing? In 1. 2. 3. 4. 5. DB testing we need to check for, The field size validation Check constraints. Indexes are done or not (for performance related issues) Stored procedures The field size defined in the application is matching with that in the db.

3) How to Test database in manually? Explain with an example Observing that operations, which are operated on front-end is effected on back-e nd or not. The approach is as follows: While adding a record thru' front-end check back-end that addition of record is effected or not. So same for delete, update,...... Ex:Enter employee record in d atabase thru' front-end and check if the record is added or not to the back-end( manually

Potrebbero piacerti anche