What is the difference between System Testing and End-To-End Testing

System testing is the testing system as the whole t.e. system is working fine.end to end testing is the testing of system from requirement specification to the delivery of phase.


System Testing:
System testing means we have to check to whole software step by step. for exmaple check the bank details. if you want transfer the amount from one account to another.that time the user goahed and check all the condition for details. this is called System Testing.

End To End Testing:
End to End testing means we are taking real time data and interacting with hardware and network.

What methodologies have you used to develop test cases?

There are mainly 3 methods to Design a test case..

1) Error Guessing ( May not be a Official Process )

2) Equivalence Partitioning

a) If the input is a Set of Value then take 1 valid and 2 invalid values

b) If the input is a Range of Values then take 1 valid and 2 invalid values

c) If the input is Boolean value then test for both True and False values

d) Lastly Devide the whole range of input values in to some equal part and

take all valid values with 2 invalid values

3) Boundary Value Analysis


Error Guessing: The tester has to guess what fault might occur and to design the tests to represent them.

Equivalence Class Partitioning: In this method the input domain data is divided into different equivalence data classes. This method is typically used to reduce the total number of test cases to a finite set of testable test cases, still covering maximum requirements.

In short it is the process of taking all possible test cases and placing them into classes. One test value is picked from each class while testing.

Boundary value analysis: It?s widely recognized that input values at the extreme ends of input domain cause more errors in system. More application errors occur at the boundaries of input domain. ?Boundary value analysis? testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain.

Boundary value analysis is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes.

What are the roles of White-box and Black-box testing tools?

Black-box testing: It is not based on knowledge of internal design or code.Tests are based on requirements and functionality.

Black box testing is used to find the errors in the following

1) Interface errors

2) Performance errors

3) Initialization errors

4) Incorrect or missing functionality

5) Errors while accessing external database

Glass-box testing: It is based on internal design of an application code.Tests are based on path coverage,branch coverage,statement coverage. It is also known as White Box testing.

White box test cases can check for..

1) All independent paths with in a modules are executed atleast once

2) Execute all loops

3) Exercise all logical decisions

4) Exercise internal data structure to ensure their validity

Black bix testing: Testing the functional and non functional charactristics ( like realibity, portability,maintainability), by refering to test basis ( requirement or design specification) with out reference to the code or structure. Models or texts are the basis of functional testing. Non-functional characteristics are quantified in terms of responce times or Mean time between failures or Mean time to repair.

White box testing is the method of testing the funcational and non functional characteristcs with refrence to internal structure or code.

What's the role of documentation in QA?

Critical. QA practices should be documented such that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals, etc. should all be documented. There should ideally be a system for easily finding and obtaining documents and determining what documentation will have a particular piece of information. Change management for documentation should be used if possible.

What is base lining?

Baselining :Process by which the quality and cost effectiveness of a service is assessed, usually in advance of a change to the service. Baselining usually includes comparison of the service before and after the Change or analysis of trend information. The term Benchmarking is normally used if the comparison is made against other enterprises.

For example :If the company has different projects.For each project there will be seperate test plans.This test plans should be accepted by peers in the organization after modifications.That modified test plans are the baseline for the testers to use in different projects.Any further modifications are done in the test plan.Present modified becomes the baseline.Because this test plan becomes the basis for running the testing project.



IN baseline approach ,in each and every phase of the development a validated output is documented which will be used as a evidence for the management.....

What if the project is not big enough to justify extensive testing?

Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed. The tester might then do adhoc testing, or write up a limited test plan based on the risk analysis.

What should be done after a bug is found?

After a bug is found it needs to be reported to the development team to get it fix.Give the developers something to work with so that theycan reproduce the problem.
1)Give a brief description of the Problem.Explain what is wrong.
2)List the steps that are needed to reproduce the bug.
3)Supply relevant information such as:
a)Version
b)Product
c)Data Used
4)Suppy the Documentation.If the Process is a report,include the copy of report with the problem area highlighted.
5)Summarize what you think the problem is.

what is debug mode in qtp

Debug mode in qtp is a temporary results folder.That means if we run any test in debug mode then the results will be stored in temporary results folder(without wasting the database memory).

Debugging is the process of executing the script in the user defined fashion with some temporary breaks in order to find errors in the script.There are 3 step commands for debugging
1.step into
2.stop out
3.stopover.

What is difference between the test effort and the test procedure?

Both are different concepts. Test effort defines how much time required to execute a particular test case. Test procedure defines the required actions to execute that test case.

what is the difference b/w system testing and functional testing

unctional Testing



Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. Functional Testing Black-box type of testing geared to functional requirements of an application. Testers should perform this type of testing.



System Testing



Upon completion of integration testing, the Test Team will begin system testing. During system testing, which is a black box test, the complete system is configured in a controlled environment to validate its accuracy and completeness in performing the functions as designed. The system test will simulate production in that it will occur in the "production-like" test environment and test all of the functions of the system that will be required in production. The Test Team will complete the system test. Prior to the system test, the unit and integration test results will be reviewed by Software Quality Assurance (SQA) to ensure all problems have been resolved. It is important for higher level testing efforts to understand unresolved problems from the lower testing levels. System testing is deemed complete when actual results and expected results are either in line or differences are explainable/acceptable based on client input.



Objective of System testing is to verify that the system is completely functional and robust enough for user interaction and use. System testing covers many different aspects including functional testing, volume/performance testing, and multi-user testing.

1)Functional Testing:-It is one of the testing type and related to functionality of systm or component that 'What it does'.
It focuses on suitability,interoperability,security,accuracy and compliance.

2)System testing:- It is one of the test level and concerned with the behavior of the whole system/product as defined by the scope of a development project or product,it is process of testing an integrated system to verify that it meets specified requirements.sustem testing should investigate both functional and non-functional requirementsof the system.

How do you get programmers to build testability support into their code?

The programers should add comment attached with their code

for a white box tester ... as for products the source code will be changed as per requirements and developers or testers who follow them should understand the logic of code easily

Developer has to write the Unit test cases and execute the same or else even they can do Automate the Unit Test cases using JUnit if the Project developed using JAVA technology. that is the proof and green signal to Tester to start the Testing.

How do you test if we have minimal or no documentation about the product?

Exploratory or ad hoc testing- it means testing the application without knowledge of documentation

Also we should get talking with the Developers and Business Analyst to undertsand the functionality and also how the product is supposed to perform. Once we understand this it would be the right way to continue testing.

What is 'Software Testing'?

Testing involves operation of a system or application under controlled conditions and evaluating the results (eg, 'if the user is in interface A of the application while using hardware B, and does C, then D should happen'). The controlled conditions should include both normal and abnormal conditions. Testing should intentionally attempt to make things go wrong to determine if things happen when they shouldn't or things don't happen when they should. It is oriented to 'detection'. (See the Bookstore section's 'Software Testing' category for a list of useful books on Software Testing.)
? Organizations vary considerably in how they assign responsibility for QA and testing. Sometimes they're the combined responsibility of one group or individual. Also common are project teams that include a mix of testers and developers who work closely together, with overall QA processes monitored by project managers. It will depend on what best fits an organization's size and business structure.
software testing is a way to identify defects in a s/w product, software testing is the most important phase in any software development project, so that we can know whether our project or product is going to be successful or it will fail before it goes live

we can define software testing as process use to identify the quality of developed computer software, so that the developer of software can compare the results produced by the finished software and the expected one. Through testing we cannot get totally bug free software we cannot achieve complete correctness through testing, but at least we can find some defects, which are there in the software

What makes a good QA or Test manager?

A good QA, test, or QA/Test(combined) manager should:
1. be familiar with the software development process
2. be able to maintain enthusiasm of their team and promote a positive atmosphere, despite
3. what is a somewhat 'negative' process (e.g., looking for or preventing problems)
4. be able to promote teamwork to increase productivity
5. be able to promote cooperation between software, test, and QA engineers
6. have the diplomatic skills needed to promote improvements in QA processes
7. have the ability to withstand pressures and say 'no' to other managers when quality is insufficient or QA processes are not being adhered to
8. have people judgement skills for hiring and keeping skilled personnel
8. be able to communicate with technical and non-technical people, engineers, managers, and customers.
9. be able to run meetings and keep them focused

He should be able to identify the test strategy based on the scope of the release to minimise the stress on the team.

What is a 'test plan'?

Test Plan is a high level document which intimates how a product will pass the testing activities, which will vary from product to product. Generally reputated organisations will follow the IEEE standard Test Plan format. The test plan consists about the resources utilization right from the manpower to the hardware info. This also mentions the test cases developed based on requirements, and further how to cater the changes (and updation of test cases or scripts), how test bench should be configured what are the resources required to establish the test bench, deployment structure, implementation architecture etc.

Test Plan should containing the details about the testing process. It is prepeared during the project planning phases.It should be containing the details about the resources to be requred, the testing approches to be followed, and test methedologies,test case etc.

What is pairwise testing?

Pairwise testing is an effective test case generation technique that is based on the observation that most faults are caused by interactions of at most two factors. Pairwise-generated test suites cover all combinations of two therefore are much smaller than exhaustive ones yet still very effective in finding defects.

What is tracebility matrix

Traceability Matrix is one of the document will prepare by QA.To make sure all the requirements mentioned in the requirements document are covered in your testing, we will prepare the traceability matrix.this document contains the following columns.Req#, Brief description about the requirement, test script ( to know in which test script it is covered), Test case .

Tracibility matrix is the document in which the test cases id's are mapped to each & every requirement.so that we can trace that all the requirements are covered with the test cases.

How to prepare document for SRS & URD?

first time write user requirenment and understand it and write in srs then write the s/w name then prepare existing of the system then prepere propose system after write the require configuration of that develope s/w then select the platform ex-.net,java,c++ e.t.c..and choose the the database ex-sql,access,oracle e.t.c..
then write user manual in short

What is the role of tester in SDLC cycle

In the SDLC the tester should be involved at the beginning of the discussion, inception, analysis. Most will try and say not unit the Software Requirements Spec. (SRS) is written ... but not true. Testing should be involved from inception to the production phase of a project.