IT Online Training in USA

  Stress testing is a  performance testing  type. It is used to test the performance of the software with varying resources. Stress testing tests the  stableness and reliability of the system. This test mainly specifies the robustness and error handling in heavy load conditions. This test specifies how system works under the extreme conditions. Stress testing is mainly used to check whether the system should not crash under extreme situations. This testing is also known as endurance testing. The main use of this testing is to set the limit whenever the software or hardware crashes. Stress testing is valuable for the reasons like ·          The system works in abnormal conditions ·          To display proper error message under stress condition ·          The system failure under stress condition can lead to revenue loss ·          It is prepared to deal with extreme conditions by doing stress testing For example – identify the number of servers required by the softw

Soak testing is a type of  performance testing  which tests the system’s performance characteristics and stability over a long period of time, ie. under continuous usage of the software. It handles issues related to memory allocation, log files and database resource utilisation. It is a system level of testing to find whether the system will stand up to very large volume of data usage over longer period of time and observing the  effect caused to the design. Characteristics of soak testing: The soak testing characteristics are ·          The duration of soak test is determined by the time available. ·          Any application should run without any disturbance if it requires over a longer period. ·          It should cover all the situations which are agreed upon with stake holders. ·          All system has its maintenance window period of time and the time between those window periods is the key driver for determining the scope of soak test. For example in an mobile

  We all know about the  integration testing  in that we test the standalone modules which are combined and tested as a single entity. There are two popular types of integration testing one is top down approach another one is bottom up approach. In hybrid testing we use the advantages of top down and bottom up approaches and the test is done by using both techniques. This is also known as sandwich testing. hybrid testing The features of Hybrid testing are: 1.        It has three layers namely: The main target layer, the layer above the target layer and the layer below the target layer. 2.        The testing is focused on the middle level target layer and is selected based on the characteristics of the structure of the code 3.        Hybrid testing is adopted if the user wants to work on the working version of the application as soon as possible determine to produce the basic working system in the earlier stages of the development cycle. The main obj

What is Manual testing? Manual testing  is the oldest and most rigorous testing method.  Manual testing  requires a tester to perform manual test operations to find defects in a software or application. The tester ensures that’s the software meets its requirements by writing, understanding and executing  test plans  and  test cases . Pros ·          If the test case only runs twice a coding milestone, it most likely should be a manual test. ·          Less cost than automating ·          It allows the tester to perform more  ad-hoc (random testing).  In my experiences, more bugs are found via ad-hoc than via automation. ·          The more time a tester spends playing with the feature, the greater the odds of finding real user bugs. Cons ·          Running tests manually can be very time consuming ·          Each time there is a new build, the tester must rerun all required tests – which after a while would become very mundane and tiresome. What is Automation test

Software testing can be either performed as manual testing or  automation testing . There are different automation testing frameworks like: data driven testing, keyword driven testing and hybrid framework.   In keyword driven testing, the keywords or actions are created for  automation testing . A keyword or an action is defined as a combination of test objects which explains how the test lines should be executed. An action word contains many arguments and is defined by the test analysis. The keyword driven testing is also known as table driven or action word testing which is software testing process that is usable for both manual and   automated testing . The process uses keywords or action words to symbolise the functionality which is to be tested such as ‘enter client’. The keyword ‘enter client’ is to be defined as a set of actions that must be executed to enter the new client in the database. The keyword documentation contains ·          The initial state of the system under