Question { TCS, 16997 }

What is Desktop Testing?

Answer

Desktop testing is nothing but "TESTING IS DONE WITHOUT INTERNET CONNECTION".

From the above point it is true that, desktop testing can done without any internet connection.

EXAMPLE:
consider an example, now we are going to do PERFORMANCE TESTING of certain web page.

For performance testing we must need internet connection.

but here in DESKTOP TESTING it can be done without internet connection.

HOW IT CAN BE DONE?

Because in desktop testing we are going to maintane separate
server for our testing.

Thus, from the above deep explanation we can under stand about the desktop testing.

Question { 11888 }

What is the difference between testing and Quality Assurance?

Answer

Difference between testing and Quality Assurance:

The difference is that Quality Assurance is process oriented and Testing is product oriented.

The goal of testing is to find the errors.

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

Testing : Finding the bugs.

QA: Prevetion of the bugs.

Testing: The process of executing a system with the intent of finding defects.

Testing for quality isn't assuring quality, it's controlling it.

Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives.

Quality Assurance makes sure you are doing the right things, the right way.

Testing is done by tester to find the errors in the project hre we check the build product is correct or not. it is validation.

Quality assurance is done by the developer while they are in the developing the project (bug free product) here we check whether we are building the right product. it is verification.

Testing is a skill of checking the software agianst user requirement.

QA is the team that provide the guidelines, standard, planning to the software company and it will verify the working methadology of the software company.

Quality assurance is creating or streamlining existing testing techniques/protocols/procedures to create a quality product.

Quality assurance will make sure correct and apt quality guidelines and procedures are set for the QC department to test a product.

Testing is the act of performing some checks or tests to make sure the product under test adheres to the quality standards and requirements (shape, size, colors etc).

Quality:

Quality means consistently meeting user requirements in terms of cost , delivery schedule & service.

Quality Assurance (QA):

- QA is planned and systematic way to evaluate quality of process used to produce a quality product.

- The goal of a QA is to provide assurance that a product is meeting customer’s quality expectations.

- QA deals with how to prevent bugs from occurring in a product being developed.

- Software Quality Assurance Engineer’s main responsibility is to create and implement methods and standards to improve development process.

- QA is associated with activities like measuring the quality of process used to develop a product, process improvement and defect prevention.

- It consists of auditing and reporting procedures related to development and testing.

Software Testing:

- Software testing is a planned process that is used to identify the correctness, completeness, security and quality of software.

- Testing is generally done to demonstrate that the software is doing what it is supposed to do as well as the software is not doing what it is not supposed to do.

- The goal of testing or software tester is to locate defects and make sure that they get fixed.

These are the basic differences between the Quality Assurance and Software Testing concepts.

Question { 13064 }

Difference between Black & White box testing

Answer

Black Box Testing:

Testing input/output without knowledge and/or regard of the internal code.

Commonly designed/executed by test team.

Black Box testing is also known as behavioural or closed box testing.

It is a software testing technique in which the internal workings of the item to be tested are not known to the tester or they are not taken into consideration.

Testing based on an analysis of the specification of a piece of software without reference to its internal workings.

The goal is to test how well the component conforms to the published requirements for the component.

White (Glass) Box Testing:

Testing input/output with full knowledge and/or regard of the internal code.

Commonly designed/executed by Developers.

White Box Testing is also known as structural,open box, clear box or glass box testing.

It is a software testing technique in which an explicit knowledge of the internal workings of the item to be tested are tested.

Testing based on an analysis of internal workings and structure of a piece of software.

Includes techniques such as Branch Testing and Path Testing.

Also known as Structural Testing and Glass Box Testing.

The basic difference between black box and white box testing is that in Black box testing we test only the external features by giving different combinations of inputs and their responses.

Black box testing is otherwise known as Specification based testing or Functional based testing.

Question { 19559 }

What is IEEE? Why is it important?

Answer

IEEE stands for Institute of Electrical and Electronics Engineers.

IEEE is dedicated to keeping its members, authors and mission safe from the effects of piracy.

Piracy of IEEE Intellectual Property (IP) not only hurts IEEE as an organization, but it can also hurt the IEEE member, subscriber and author.

Question { Millennium, 8829 }

what do u like in QA?

Answer

In software engineering Quality Assurance is one of the important play.

Their work is to assure the project whether the project in good path or not.

For Quality Assurance the work load and work pressure is very less.

Question { 62307 }

What is batch testing?

Answer

Batch testing is an integral part of Wild Country's quality system.

It is a process in which one test is done simultaneously on multiple specimens.

Steps for Batch Testing:

1). Prepare Individual Tests and Run once.

2). Open Test batch Runner Tool and Form Batches.

3). Run or Execute Test Batches from Test Batch Runner.

Question { 8708 }

What is an IDE?

Answer

INTEGRATED DEVELOPMENT ENVIRONMENT:

IDE(integrated development environment)is a software application that provides comprehensive facilities to computer programmers for software development.

An integrated development environment also known as integrated design environment, integrated debugging environment or interactive development environment.

An IDE normally consists of:

1. a source code editor.
2. a compiler and/or an interpreter.
3. build automation tools.
4. a debugger.

The boundary between an integrated development environment and other parts of the broader software development environment is not well-defined.

Sometimes a version control system and various tools are integrated to simplify the construction of a GUI.

Many modern IDEs also have a class browser, an object inspector, and a class hierarchy diagram, for use with object-oriented software development.

Question { 9209 }

what is metrics?...What metrics do u follow in ur company?

Answer

metrics:

Measurement is fundamental to any engineering discipline.

- We cannot control what we cannot measure.
- Metrics helps to measure quality.
- Serves as dash-board.

The main metrics are: size, shedule, and defects. In this there are main sub metrics.

Test Coverage = Number of units (KLOC/FP) tested / total size of the system.

Test cost (in %) = Cost of testing / total cost *100.

Cost to locate defect = Cost of testing / the number of defects located.

Defects detected in testing (in %) = Defects detected in testing / total system defects*100.

Acceptance criteria tested = Acceptance criteria tested / total acceptance criteria.

Question { 5411 }

what is web testing and what should you test in web testing?

Answer

WEB TESTING:

This is done for 3 tier applications (developed for Internet / intranet / xtranet).

Here we will be having Browser, web server and DB server.

The applications accessible in browser would be developed in HTML, DHTML, XML, JavaScript etc. (We can monitor through these applications).

Applications for the web server would be developed in Java, ASP, JSP, VBScript, JavaScript, Perl, Cold Fusion, PHP etc. (All the manipulations are done on the web server with the help of these programs developed).

The DB server would be having oracle, sql server, sybase, mysql etc. (All data is stored in the database available on the DB server)

Web testing includes,

1. Performance testing.

2. load testing.

3. functional testing.

4. Static web testing.

5. Frame work testing.

6. Client/serve testing.

Question { 6789 }

how to do manual test?

Answer

In simple term "MANUAL TESTING IS DONE BY MANUALLY".

The above point consist of lot of meaning and true that, manual testing is done only by manually.

EXAMPLE:
consider we are going to find page load time for a particular web page. It can done only by manually.

Automated testing will never sute for finding page load time and for small projects we can't use automated testing.

Question { Semantic Space, 10728 }

what is the format of test report?

Answer

The following are the formats of test report:

Section I
Basic Information:
1) Packaging manufacturer's name and address;
2) Packaging component (cap, inner package, etc,) manufacturer's name and address, if different from
above;
3) Testing laboratory's name and address (if different from (1));
4) Unique test report identification number;
5) Date of the test report;
6) Signature of certifier and name and title.

Section II
Packaging Description – Applicable to all design types; additional design specific information is provided in the appropriate packaging design standard.
1) Packaging design standard (UN 1A1, UN 4G, UN 6HA1, etc) and trade name.
2) Materials of construction of the packaging body, heads, lid, etc;
a) Type and grade
b) Thickness
i) Minimum
ii) Nominal
3) Method of construction
4) Capacity
i) Nominal
ii) Maximum
5) Dimensions, external – see appropriate design type for additional required information;
6) Closures – see appropriate design type for additional required information;
7) Tare mass of complete packaging and individual components;
8) Filled mass of package as tested;
9) Closure method
a) Equipment used to close the package; and
b) Description of a repeatable and consistent means of closure.
10) Inner receptacles and inner packagings – see appropriate section for additional required information;

Section III
Test Description and Results
1) Test method;
2) Conditioning (if required);
3) Test contents, material used, viscosity and relative density for liquids (if other than water and antifreeze) and particle size for solids;
4) Pass/Fail criteria
5) Test results

Section IV
Mathematical Calculations performed to conduct and document testing.
1) Packaging fill limits to determine 95% or 95% full for testing;
2) Drop height for high specific gravity liquids;
3) Stacking test load;
4) Other calculations as required.

Section V
1) Packaging design drawings for all packaging components.

Question { 11151 }

what is boundary value analysis?

Answer

‘Boundary value analysis’ testing technique is used to identify errors at boundaries rather than finding those exist in center of input domain.

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 is a next part of Equivalence partitioning for designing test cases where test cases are selected at the edges of the equivalence classes.

Boundary value analysis is often called as a part of stress and negative testing.

TEST CASES:

1) Test cases with test data exactly as the input boundaries of input domain i.e. values 1 and 1000 in our case.

2) Test data with values just below the extreme edges of input domains i.e. values 0 and 999.

3) Test data with values just above the extreme edges of input domain i.e. values 2 and 1001.

Question { 6872 }

What is a Module?

Answer

Module:

Module consist of sub programmers.

sub programmer consist of sub functions.

Collections of modules are called Projects or applications.

Question { CTS, 54359 }

Are monkey testing & gorilla testing same? If not, then
what is the difference between these two?

Answer

Monkey Testing and Gorilla testing are not same.



Monkey testing - an unflattering term used to describe inexperienced people "banging" on a terminal. Often used to describe testing by staff who have trouble finding their butt with both hands.

Gorilla testing - used to describe repetitive, boring manual testing that a tester has already done a hundred times and could do in their sleep. As in "a trained gorilla could execute these tests". Often a sign that testing needs to be automated.

In simple term it can be referred as following below,

Gorilla Testing - you have a real short window of time to test and X number of resources (typically experienced QA). You hit the app hard, with everyone focused on core functionality and critical paths a "typical" user would take through the app. Unfortunately, this is still all too common today.

Monkey Testing - mundane testing that you have to do when your company is too cheap to buy you an automation tool to do it for you. It's a huge waste of senior tester's time, but usually no other resources are available.

Question { 8331 }

how can u find system IP address

Answer

What Mr.G. Sunil Dhotre and Mr.Abhijit has given is totally correct.

But Mr.G. Sunil Dhotre you are Extra ordinary.

very good.

keep moving.