Showing posts with label FAQs. Show all posts
Showing posts with label FAQs. Show all posts

Wednesday, 17 July 2013

FAQs on QA Testing Part-III

continue with FAQs on QA Testing Part-III
FAQs on QA Testing Part-III
What can be done if requirements are changing continuously?
Work with management early on to understand how requirements might change, so that alternate test plans and strategies can be worked out in advance. It is helpful if the application’s initial design allows for some adaptability, so that later changes do not require redoing the application from scratch. Additionally, try to…
  • Ensure the code is well commented and well documented; this makes changes easier for the developers.
  • Use rapid prototyping whenever possible; this will help customers feel sure of their requirements and minimize changes.
  • In the project’s initial schedule, allow for some extra time to commensurate with probable changes.
  • Move new requirements to a ‘Phase 2′ version of an application and use the original requirements for the ‘Phase 1′ version.

Tuesday, 16 July 2013

FAQs on QA Testing Part-II

FAQs on QA Testing Part-II
continue the FAQs on QA Testing Part-II
What will you do if developer does not accept the bug?
If the developer does not accept the defect, then he will reject it. Once it is rejected, then it comes back to the tester. Now, the tester will ask for clarification with the developer why the defect is rejected. Since everything is based on the requirement documents, both tester and developer will have to look at the requirement document, validate it and then reopen it if necessary or close.


Monday, 15 July 2013

FAQs on QA Testing Part-I

continue to reading FAQs on QA Testing Part-I
FAQs on QA Testing Part-I
What do you like about QA?
The best thing I like about QA is, I like the job which is more process oriented. For example, we have to work right from reading the requirement documents, providing feedback to the Business Analysts as necessary, writing test plans, test cases, execute the test cases, interaction with different developers, attend walk-through meeting and so on. I am a very detailed oriented person. When I test applications, I try to get into the depth of functionality so that I don’t miss out anything. Finally, I love logging defects.


What are all the basic elements in a defect report?
The basic elements in a defect report are: Defect ID, Header, Description, Defect Reported by, Date, Status, Version, Assigned to, Approved by, Module where the defect was found and so on.

Sunday, 14 July 2013

FAQs on QA Testing


Get some FAQs on QA Testing and practice it
FAQs on QA Testing
What does Test Strategy include?
It includes introduction, Test Objectives, Test Process, Test Methodology, Test Scope, Release Criteria for Testing (exit criteria), Test Lab configuration, resource and schedule for test activities, acceptance criteria, test environment, test tools, test priorities, test planning, executing a test pass and types of test to be performed.

What are different types of software testing and define them?
Different types of testing are:


1) Unit testing
2) Shakeout testing
3) Smoke testing (Ad-hoc testing)
4) Functional testing
5) Integration testing
6) Regression testing
7) System testing
8) Load testing
9) Stress testing
10) Performance testing
11) User acceptance testing
12) Black box testing
13) White box testing
14) Alpha testing
15) Beta testing
(Note: Except the Shakeout testing and Unit testing (which are respectively done by the CMT (Configuration Management Team) and Coder/Developer), all other testing are done by the QA tester.)

Wednesday, 22 August 2012

FAQs on testing


1.    With thorough testing it is possible to remove all defects from a program prior to delivery to the customer.
a. True                                                 b. False

ANSWER : b

2.    Which of the following are characteristics of testable software ?
a. observability             b. simplicity                 c. stability        d. all of the above

ANSWER : d

3.    The testing technique that requires devising test cases to demonstrate that each program function is operational is called
a. black-box testing     b. glass-box testing    
c. grey-box testing      d. white-box testing

ANSWER : a


4.    The testing technique that requires devising test cases to exercise the internal logic of a software module is called
a. behavioral testing    b. black-box testing     c. grey-box testing      d. white-box testing

ANSWER : d


5.    What types of errors are missed by black-box testing and can be uncovered by white-box testing ?
a. behavioral errors      b. logic errors  c. performance errors  d. typographical errors
e. both b and d

ANSWER : e


6.    Program flow graphs are identical to program flowcharts.
a. True                                     b. False

ANSWER : b

7.    The cyclomatic complexity metric provides the designer with information regarding the number of
a. cycles in the program                                  b. errors in the program         
c. independent logic paths in the program      d. statements in the program

ANSWER : c

8.    The cyclomatic complexity of a program can be computed directly from a PDL representation of an algorithm without drawing a program flow graph.
a. True                                     b. False

ANSWER : a

9.    Condition testing is a control structure testing technique where the criteria used to design test cases is that they
a. rely on basis path testing    
b. exercise the logical conditions in a program module
c. select test paths based on the locations and uses of variables
d. focus on testing the validity of loop constructs

ANSWER : b