SQA activities - suggesting & reviewing the process documents

Example - reviewing project management plan, etc

SQA activities are to monitor the complete software development PROCESS. It includes
continuous improvements and enhancements of the overall development PROCESS.

How can we perform testing without expected results?

Main concept in testing is the expected result. By knowing the expected behavior of the
application or system from SRS and FDS, we can derive a test case. When executed the
derived test case's, actual result is noted. Any deviation from the expected is considered as a
defect.

In Adhoc testing ,there is no need of a test case, but if we want to log a defect ,we should
know the expected behavior of the application or a system.

There is only one possibility for this question according to me. Exploratory testing.

An interactive process of concurrent product exploration, test design, and test execution. The
heart of exploratory testing can be stated simply. The outcome of this test influences the
design of the next test. Tester will explore the product or application and will note down the
expected result and will design a test case and execute the test.

Q Which of the following statements about regression testing are true? (1)
Regression Testing must consist of a fixed set of tests to create a baseline (2)
Regressoin Testing should be used to detect defects in new features (3) Regression
Testing can be run on every build (4) Regression Testing should be targeted to
areas of high risk and known code change (5) Regression Testing, when automated,
is highly effective in preventing defect

ANS: 1 & 3.

Q How do you conduct boundary analysis testing for "ok" push button

Ans: For Ok and submit buttons we can follow below testing -

1. Proper URL of Window is opening or not

2. User Interface testing

####What is an exit and entry criteria in a Test Plan ?

generally, test plan document is prepared by TL&QM.

Entry &Exit criteria is part of test plan document

Entry criteria is

1.testing environment established

2.test cases prepared

3.build received from development team

Exit criteria is

1.All modules are covered or not

2.all test cases are completely executed or not

3.all bugs resolved or not

this is part of HOW TO TEST criteria test plan document

According to me entry crieria is that when it comes to testing deparment for testing with unit
test checklist and exit crieria is when all planned test cases gets executed and no bugs
remains in the system on the basis of these test cases.

What is configuration Management?

Configuration management (CM) is the processes of controlling, coordinate, and tracking the
Standards and procedures for managing changes in an evolving software product.

Configuration Testing is the process of checking the operation of the software being tested on
various types of hardware.

Who writes the Business requirements? What you do when you have the BRD?

Business Analyst writes the Business Requirements. In a large commercial software

development environment main actors within the life cycle of a software project are as
follows: Project Stakeholder(Sponsor)Project Manager (manages the entire project)QA
Manager Business, Analyst Software, Architect Business Analyst after finalizing the scope of
the project with the Project Stakeholders(sponsors) writes all the business requirements(BR)
for the software application and then send it to software architect(SA) for validation. SA after
understanding the BR make use cases and UML diagrams and forward them to QA manager.
QA manager based on scope, BR, use case & UML diagram writes the overall testing strategy
& high level test cases and forward them to testers. Project manager monitors the complete
project. QA manager, Business Analyst & Software architect reports project manager whereas
project manager reports to project stakeholder.

What we normally check for in the Database Testing?

In DB Testing, basically all the events like Add, Delete, Update, Modify etc
What is walkthrough and inspection?

Walkthrough is there for both Testing and Coding.

Walkthrough for testing means brief review of documents, Test cases, Test script etc.

Walkthrough for Coding means review the coding for whether the Developer follows the
Coding standards or not.

Inspection is job of Quality Control (QC). He can conduct Inspections and Audits on the
project at any time to check whether the process is going on correctly or not.

I will tell y one example for Test Engineer, QA, QC

Take an Examination Center: In that

---> Test Engineer is Examiner

----> QA is sitting squad

---> QC is a flying squad

Walkthrough: Explain the work product in a step by step manner. Inspection: Also called as
"Formal Review". There is a formal process that states how this should be conducted. There
is a sharp focus finding defects

Testing: What are the key elements for creating test plan

The key elements for a test plan are:

1.Entrance Criteria: The requirement documents based on which the plan is developed. The
BRD, FRD
2.Test environment
3.Test data

How do you ensure the quality of the product?

The quality of the product can be ensured by look into the minimum bugs in a product as per
the standard maintained by the organization for the clients. That means if a company is the
six sigma oriented company then there should be at least 3-4 bugs per millions

What is the job of Quality assurance engineer? Difference between the testing &
Quality Assurance job.

A Quality Assurance Engineer is one who understands the SDLC Process. He\she has a 'test to
break attitude', an ability to take the point of view of the customer, a strong desire for qly
and an attention to detail. Communication skills and the ability to understand various sides of
issues are important.

Difference between Testing and Quality Assurance

The aim of testing is to find the Errors.

The goal of QA is to prevent the errors in the application.

Qly Assurance is a preventive action.

 **********************************************

Testing means Quality Control.

Quality measures the 'quality' of a product.

Quality Assurance measures the 'quality' of the processes used to create a quality product.

What is the role of QA in a project development?

The role of QA rank parallel to the Project Development in simulating the Framework of
Testing as per the requirements followed with Paperwork results for the Test Planning,
Design Test cases n writing the Test cases subsequent to this, Implementing the Metrics,
Delivery of the Product as per the Deadlines Etc.,

How can u test the white page?

You can check whether the dimensions of the paper and print jobs are from the
requirements document. Canvas sizing, resizing, window minimize and maximize functions,
Line scroll and Page scroll are other areas to test

What is the role of QA in a company that produces software?

QA is responsible for managing, implementing, maintaining and continuously improving the

Processes the Company and enable internal projects towards process maturity and facilitate
process improvements and innovations in the organization.

Tester is responsible for carrying the testing effort in the company.

In many companies QA position is for doing the role of both Testing and creating and improving
the processes.

Describe to me when you would consider employing a failure mode and defect
analysis?

When product is not as per the functional document specification then we considers it as
employing the failure mode and defect analysis.

In general, how do you see automation fitting into the overall process of testing?

Using automation method is adopted if our process is repeatable in nature and the time taken
to do manual ways are not efficient and economical. We adopt the testing to be done using
automation tools either already available or developed own script/software to do the testing
process

Describe to the basic elements you put in a defect report?

Bug report contains complete details of bug. Which are

bug identifier
bug description
status: (New, open, fixed, closed, reopen)
severity: (blocker, major, minor cosmetic)
detected by
detected on date
product version
platform
reproducible or not

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.White Box Testing 2.Black Box 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, UAT
(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
and also to answer two questions
1· Whether the system is doing what it supposes to do?
2· Whether the system is not performing what it is not suppose to do?

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. What is test metrics?

A.

9. 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
things

Even 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.

10. What are the entry criteria for Automation testing?

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

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, within 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
customer
requirements r not .It is a static process.

15. What is validation?

A. To check whether we have developed the product according to the customer
requirements 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 Proces.

17.What is quality control?

A. Quality control measures the quality of a product
1.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.Analysis
3.Design 4.Coding
5.Testing 6.User acceptance test(UAT)
7.Maintainance

Software Test Life Cycle(STLC) is a life cycle of the testing process.

1.Requiremnts Specification. 2.Planning
3.Test case Design. 4.Execution
5.Bug Reporting. 6.Maintainance

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.When to start and Stop Testing?

A. repeat

21.What are the various levels of testing?

A. The various levels of testing like
1· Ad - Hoc testing
2. Sanity Test
3. Regression Testing
4. Functional testing
5· Web Testing

22.What are the types of testing you know and you experienced?
A. I am experienced in Black Box testing.

24.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.

25.What is a Test Bed?

A. Test bed means under what test environment (Hardware, software set up) the
application will run smoothly.

26.What is a Data Guidelines?

27.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,then
only we can run the application smoothly without any intereptions.

28.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.
Severity:How sevierly the bug is effecting the application.
Priority:Informing to the developer which bug to be fix first.

29.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.

30.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.

31.What is a test condition?

A. The condition required to test a feature.(pre condition)

32.What is the test script?

A. Test script is the script which is generated by an automation tool while
recording a application features.

33.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.

34.What is an Inconsistent bug?

A. the bug which is occurring

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

A Re-testing:Executing the same test case by giving the no. of inputs on same
build.
Regression testing:Executing the same test case on a modified build.

36.What are the different types of testing techniques?

A. 1.white Box testing 2.Black Box testing.

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

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

38.What are the risks involved in testing?

39.Differentiate Test bed and Test Environment?

A. Both are same.

40.What ifs the difference between defect, error, bug, failure, fault?
A. Defect: While executing the test case if u found any mismatch, then u will
report
it to the development team, that is called defect.

Bug: Once the developer accepts your defect, then it is called as a bug.

Error: it may be program error or syntax error.

41. 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.

42. 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.

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

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

44.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.

45.What is the difference between bug and defect?

A. Defect:While executing the test case if u found any mismatch,the u will
report
it to the development team,that is called defect.

Bug:Once the developer accepts your defect,the it is called as a bug.

46.What is the difference between verification and validation?

A. Refer Question no.14 & 15

47.What is the difference between functional spec. and Business requirement

specification?
A. BRS is the crude business language which is stated by the
client and can't be processed to design stage based on this
document.

FRS/FSD is a document prepared by the business analyst and a

baseline document for the SDLC/STLC process. Though, FSD is
prepared with the help of BRS only but FSD contains more
technical terms and prepared keeping technical aspects of SDLC

48.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. 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.

49. What is the diff between Volume & Load?

A. Load,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.

50. What is diff between Volume & Stress?

A. Refer Question no.49

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

A. Refer Question no.49

52. 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.

53. What is the diff between Client Server & Web Based Testing?
A. Refer Question no.52

54. 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.

55. What is the Diff between Code Walk through & Code Review?
A: Code Walkthrough: A formal testing technique where source code is traced by a group with a
small set of test cases, while the state of program variables is manually monitored, to analyze the
programmer's logic and assumptions.
Code Review: A meeting at which software code is presented to project personnel, managers,
users, customers, or other interested parties for comment or approval.

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

A. Walkthrough: A 'walk through' is an informal meeting for evaluation or informational
purposes. Little or no preparation is usually required
Inspection: 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.

57. What is the Diff between SIT & IST?

58. 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 through and desk checks.
Dynamic testing: Test activity that is performed by running the software is called dynamic
Testing.

59. What is the diff between alpha testing and beta testing?
A. Alpha Testing: Alpha testing will be performed by 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, In this
phase no bugs can be allowed.