Software Testing Experts

Stress Testing is the testing to verify the response/output of the software beyond the breaking point of the system. In Stress Testing, Test team focus on robustness, availability and the error handling under the heavy load rather then correct behavior under normal circumstances. It is the type of non functional testing.

In Volume Testing, application is test with the huge amount of data as name applies. Volume Testing is the Non-Functional Testing. When tester test the volume Testing, we need to extend the size of the database to store the large amount of data.

A Soak Testing is a typical production load for continuous available period to check system behavior under production use.  Soak Test also called the Endurance Test. It is a non-function Testing.

Meaning of Load Testing is to provide constantly or steadily  load for a software to check that how software is responding in increasing load without significant performance degradation. Load Testing is put load over the system to check the response. We increase the limit until the threshold limit. In Load Testing we determine the system limit in normal load and peak load limit of the system. If we increase the load then peak to check system response this will called the Stress Testing .

Performance Testing is the testing in which Test Team determine how the system will perform in terms of responsiveness and when the system will be overloaded. In Performance Testing , we validate or verify the scalability, reliability and how the system uses the available resources. These all are the quality attribute of the system.

In the terms in programming context, build is the version of the program. Build is the executable code which is used for the Testing Purpose. Build is just the version for the testing team to test the software before release it to the customer.

Sanity Testing is perform when QA team received the build after fixes of minor bugs or some new functionality added. In Sanity Testing, QA team check that the bugs that generated in last build should be fix and due to those bug fixes there should be no new bugs generated. So in Sanity Testing first QA team check the regression testing and after regression testing QA team verify the previous bugs.

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.

Beta Testing comes after the Alpha Testing. In Beta Testing, product is release outside from the organisation ( Outside from the Testing Team) for the public users to find out the issues or fixes or feature which left from the developer and tester team within the organisation. Beta Testing is the testing which is perform by the real world users in real environment and it is perform at client location or end user of the software.

Alpha Testing is the type of Acceptance Testing. Alpha Testing occur when the development part is about to complete and some small design changes are happening. The main intention of Alpha Testing to check the complete software before release it to the customer or the end users.

Error: Any mistake in the coding called error. The mistake may be Syntax error, Logical errors or other GUI errors lead errors in any software. These are from developer side. Defect: The error which made by developer and during testing, Tester is able to find that errors,  means if actual result deviated from expected result then that error called defects. This is caught by testers. Bug: The defect which is developed by tester team, if expected by the developer team then that defect called an bug. Failure: If the Software does not meet the client requirement then this is called failure of the software. 

For successful completion of any project depend on it's testing and testing totally depends over Test Cases. So here i am explaining all the techniques of Test cases Designing.

Functional Testing is a Quality Assurance process in which, QA team provide the input to the function and check the output without checking the internal structure of the function. This is a Black Box Testing. In the Function Testing, Test team provide the input and check the output to validate that whether the output matching with the expected output.

In Usability Testing, we verify that the system should be easy to use for the end users. The Main Focus in this testing to make software easy to use, flexible, attractive, easy to operate, easy to learn, fast and system should meet it's objective. Usability Testing done with end user perspective Usability Testing is the Black Box Testing and also Non Functional Testing .

Acceptance Testing is the formal testing as per the user needs, requirement and the business requirement to determine whether system satisfies the acceptance criteria and enable the user or customer to determine weather to accept the system or not. Acceptance Testing is perform after the all errors and defects fixes in the System Testing. Acceptance Testing perform by the customer or stakeholder.Acceptance Testing is the last phase of the software testing process.

In GUI Testing, we verify the user interface of the software and to check this user interface with the specified requirement. User interface means the color, font, font size, Text format, Text Box, Radio Button, Checkbox, Buttons, icons, alignment, links , pop up , contents, Menu bar, Dialog bar,  Tool bar and so many. Following is the check list that what we need to test in GUI Testing

System Testing is the software testing to integrate whole system and verify the functionality of the system with the specified requirement. This is the Black Box testing so no knowledge regarding code is required. This is End to End Testing. System testing basically to exercise of whole system when all interfaces combined with each other. In System Testing we check the behavior of the complete and fully integrated software product based on the requirement. System testing usually carried out by the Team which is independent of the Development Team to work with new mind for finding new bugs.

When all small unit of code combined together or we can say integrate together then perform the testing between the interface of these units to verify that are these unit working fine when these are combined. Integration Testing occur after Unit Testing. In Unit Testing , developer concern only over the each module and fixes all error in that but developer not focused that what is the effect of bug fixes in other modules. Each Unit is developed by different different programmers so in Integration Testing, We will test the data communication between these Units.

Unit Testing is the smallest testable part of the software.  It may be a function, Class, procedure and the Interface. In Unit Testing individual unit of source code are tested to determine whether they are fit for use. Unit Testing is the short source code testing which is done by programmer or done by white box tester during the development process. This testing mode is component of Extreme Programming (XP), which means developing a product with continuous testing and revisions.

Sometimes in interviewer ask about the difference between Test Case and Test Suite and the interviewed get confused for this question. Now i am providing the definition of Test Suite. Test Suite is the collection of some specific set of behaviors Test Cases which are used to test the software. A Test Suite contains the detailed instruction of each collection of Test Cases which are used for testing. A Test Suite also contains the prerequisite steps and the description of the following steps.