Difference between Functional and Non-Functional Testing

Functional Testing: 

1. Testing the application against business requirements. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.
2. Functional testing is concerned only with the functional requirements of a system or subsystem and covers how well (if at all) the system executes its functions. These include any user commands, data manipulation, searches and business processes, user screens, and integrations.
3. Functional testing is done using the functional specifications provided by the client or by using the design specifications like use cases provided by the design team.

what is Ad-hoc and Exploratory Testing

Ad-hoc Testing

1. Ad hoc testing is a commonly used term for software testing performed without planning and documentation.
2. The tests are intended to be run only once, unless a defect is discovered.
3. Adhoc testing is the least formal test method.
4. The strength of ad hoc testing is that important defects can be found quickly.
5. A creative and informal way of testing the software
6. Conducted without any understanding of the software before testing it
7. Not conducted based on formal test plans or test cases
8. Performed by Testers
9. Performed on a Stable application or product.

Difference between smoke testing and sanity testing

Smoke Testing

Software Testing done to ensure that whether the build can be accepted for through software testing or not. Basically, it is done to check the stability of the build received for software testing.

In Smoke Testing, the test cases chosen cover the most important functionality or component of the system. The objective is not to perform exhaustive testing, but to verify that the critical functionality of the system are working fine.

For Example a typical smoke test would be - Verify that the application launches

Dhanush InfoTech Pvt Ltd recruiting for “Oracle Apps – Technical Manager” in May-2014

Dhanush InfoTech Pvt Ltd recruiting for “Oracle Apps – Technical Manager” in May-2014

Company Name

Dhanush InfoTech Pvt Ltd

Job Role

Oracle Apps – Technical Manager

Job Location

Gurgaon, India

Dhanush InfoTech Pvt Ltd recruiting for “Oracle Apps Functional - SCM (supply Chain Management)” in May-2014

Dhanush InfoTech Pvt Ltd recruiting for “Oracle Apps Functional - SCM (supply Chain Management)” in May-2014

Company Name

Dhanush InfoTech Pvt Ltd

Job Role

Oracle Apps Functional - SCM (supply Chain Management)

Zen3 Info solutions Ltd recruiting for “PPC Manager (Pay Per Click)” in May-2014

Zen3 Info solutions Ltd recruiting for “PPC Manager (Pay Per Click)” in May-2014

Company Name

Zen3 Info solutions Ltd

Job Role

PPC Manager or Paid Search Manager/ Executive

User Acceptance Testing with alpha and beta testing in software testing

User Acceptance Testing:

In the case of software, User acceptance testing (UAT) is the last phase of the software testing process. Acceptance testing performed by the customer is known as User Acceptance Testing (UAT), end-user testing, site (acceptance) testing, or field (acceptance) testing.

• Conducted just before the software is released to production
• Tests system's readiness for deployment and use.
• Performed by the end-users from the client’s team with a certain set of test cases and typical scenarios
• Goal is to establish confidence in system.
• Finding defects not the main focus.
• Demonstrates to the customer that predefined acceptance criteria have been met by the system
• Acceptance criteria may be define by the customer or approved by the customer