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

Regression testing and Retesting in software testing

Regression Testing

• It is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality.
• It is executed after enhancement or defect fixes in the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle.
• Every time after making changing in the existing working code, a suite of test case have to executed to ensure that changes are not breaking working features and not introduced any bugs in the software. It is essential to prepare such test suite & executed on every newer version of software. Also to automate the regression testing this test suite will help to create an automated testing script.

Difference between Test Scenario and Test Case in software testing

Test scenario:

• Test scenario is nothing but test procedure. A Test Scenarios have one too many relation with Test case, Means A scenario have multiple test case. Every time we have write test cases for test scenario
• Which will tells about functionality and it will be written by tester.
• During test analysis and design phase with the test basis as the input one would start identifying test condition and would determine high level test scenarios from these test conditions. At the later stages of test design 'concrete' test cases are defined from these test scenarios. One should be able to derive multiple test cases from one high level test scenario. 

Unit testing and System Testing in software testing

Unit Testing:-

•       Testing of Individual Unit (E.g. : Function, Program, Module)

1.       Also referred to as White Box Testing

2.       Typically performed by the Developer

3.       Goal of Unit testing is to uncover defects using formal techniques like:

•       Resource-behavior (e.g. memory leaks), performance or robustness testing, as well as structural testing

•       Defects and deviations in Date formats

•       Special requirements in input conditions (for example Text box where only numeric or alphabets should be entered)

•       Selection based on Combo Box’s, List Box’s, Option buttons, Check Box’s

•       Testing occurs with access to the code being tested, with the support of the development environment, such as a unit test framework or debugging tool.

4.       The testing must ensure:

•       Statement Coverage

•       Branch Coverage

Integration testing in software testing

Integration Testing

•       Testing the Integration of multiple units / modules

–      The objective is to test the application that is built by integrating the unit tested components

–      This tests interfaces between components, interactions with different parts of a system such as O.S, hardware and interfaces between systems.

–      Testers should concentrate solely on integration itself and not functionality of the individual modules to be integrated.

•       Performed by the Developer / Tester

•       Various approaches to Integration Testing could be :

Functional testing in software testing

Functional Testing

1.       Functional Testing is a Type of Testing conducted to – test the functionality of the application with respect to the requirements

2.       Also referred to as Black Box Testing

3.       Functional test cases are derived from the functional requirements of the software and are the basis for system testing. These help you in testing if the required functionality is working as per the specifications.

·         Ensure that the system under test is operational as per the customer requirements.

·         Verify whether the application is ready for release.