Explore Software Testing Concepts!

  Unit Testing  is a type of software testing where individual units or components of a software are tested. The purpose is to validate that each unit of the software code performs as expected. Unit Testing is done during the development (coding phase) of an application by the developers. Unit Tests isolate a section of code and verify its correctness. A unit may be an individual function, method, procedure, module, or object.

Non Functional Testing Non-Functional Testing  is defined as a type of Software testing to check non-functional aspects (performance, usability, reliability, etc) of a software application. Following are the most common  Types of Non Functional  Testing: Performance Testing Load Testing Failover Testing Compatibility Testing Usability Testing Stress Testing Maintainability Testing Scalability Testing Volume Testing Security Testing Disaster Recovery Testing Compliance Testing Portability Testing Efficiency Testing Reliability Testing Baseline Testing Endurance Testing Documentation Testing Recovery Testing Internationalization Testing Localization Testing 1) Security: The parameter defines how a system is safeguarded against deliberate and sudden attacks from internal and external sources. This is tested via Security Testing. 2) Reliability: The extent to which any software system continuously performs the specified functions without failure. This is tested by R...

What is Black Box testing? In  Black-box testing , a tester doesn’t have any information about the internal working of the software system. Black box testing is a high level of testing that focuses on the behavior of the software. It involves testing from an external or end-user perspective. Black box testing can be applied to virtually every level of software testing: unit, integration, system, and acceptance. What is White Box testing? White-box testing  is a testing technique which checks the internal functioning of the system. In this method, testing is based on coverage of code statements, branches, paths or conditions. White-Box testing is considered as low-level testing. It is also called glass box, transparent box, clear box or code base testing. The white-box Testing method assumes that the path of the logic in a unit or program is known.

  Alpha Testing  is a type of acceptance testing; performed to identify all possible issues and bugs before releasing the final product to the end users. Alpha testing is carried out by the testers who are internal employees of the organization. The main goal is to identify the tasks that a typical user might perform and test them. Beta Testing  is performed by “real users” of the software application in “real environment” and it can be considered as a form of external  User Acceptance Testing . It is the final test before shipping a product to the customers. Direct feedback from customers is a major advantage of Beta Testing. This testing helps to test products in customer’s environment. Alpha Testing Beta Testing Alpha testing performed by Testers who are usually internal employees of the organization Beta testing is performed by Clients or End Users who are not employees of the organization Alpha Testing performed at developer’s site Beta testing is performed at a...

Smoke Testing   Smoke Testing a software testing technique performed post software build to verify that the critical functionalities of software are working fine. It is executed before any detailed functional or regression tests are executed. The main purpose of smoke testing is to reject a software application with defects so that QA team does not waste time testing broken software application. For Example, a typical smoke test would be – Verify that the application launches successfully, Check that the GUI is responsive … etc. Sanity testing  Sanity Testing is a kind of Software Testing performed after receiving a software build, with minor changes in code, or functionality, to ascertain that the bugs have been fixed and no further issues are introduced due to these changes. The goal is to determine that the proposed functionality works roughly as expected. If sanity test fails, the build is rejected to save the time and costs involved in a more rigorous testing. Key Differe...

Integration Testing   Integration Testing is a type of software testing where two or more modules of an application are logically grouped together and tested as a whole. The focus of this type of testing is to find the defect on interface, communication, and data flow among modules. Top-down or Bottom-up approach is used while integrating modules into the whole system. System testing  System testing is types of testing where tester evaluates the whole system against the specified requirements.  End to End Testing It involves testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. 

  Use case, test case, and test scenario are all related to software testing. Use case is a document that describes how a user interacts with a system to achieve a specific goal. Test case is a set of inputs, execution conditions, and expected results developed for a particular objective. Test scenario is a series of actions that are associated together. It represents a thread of operations. Test Cases are derived from test Scenarios which are derived from Use case. What is a Use Case? A Use Case is used to define the system that how to use the system for performing a specific task. A use case is not a part of execution it is only a diagrammatic presentation of a document that specifies how to perform a certain task. The actor simulates the end-user interaction, and it can be portrayed by human or external software. Use cases are also visualized with an overview diagram. The diagram should contain all components that are involved when interacting with the system...