Category: Software Testing

GUI Testing

GUI TestingGUI testing is a process to test the application’s user interface and to make sure that it confirms the design requirements. 1. Text Boxa. Move the Mouse Cursor over all Enterable TextBoxes. The cursor should change from an arrow to Insert Bar.b. If it doesn’t then the text in the box should be grey or non-updateable.c. Try to overflow the text by typing too many characters.d. Enter invalid characters – Letters in amount fields, try strange characters like +, – *, etc. in All fields.e. SHIFT and Arrow should Select Characters. Selection should also be possible with the mouse. Double Read More

Performance, Load, Stress, and Volume Testing

1. Performance TestingIn white-box testing testers, developers, system administrators, and DBAs work together in order to instrument the application code and the database queries (via specialized profilers for example), and the hardware/operating system of the server(s) running the application and the database (via monitoring tools such as vmstat, iostat, top or Windows PerfMon). All these activities belong to performance testing.The goal of performance testing is not to find bugs, but to eliminate bottlenecks and establish a baseline for future regression testing. These bottlenecks can exist at multiple levels:a. at the application level, developers can use profilers to spot inefficiencies in their code Read More

Manual testing concepts for beginners

Why we need a Tester ? CAR SALESMAN: The car is complete – you just need to paint it. Whatever a software organization develops should meet the needs of the customer. Testing means to make sure that the product meets the needs of the customer. If our job is to give a complete car to the customer (and not ask the customers to paint the car) then we should ensure that we catch and correct all the defects in the car ourselves. This is the fundamental objective of testing. Just Testing is not enough, we need effective testing In the Read More

Black Box, White Box, and Gray Box Testing

Black Box TestingBlack box testing refers to the technique of testing a system with no knowledge of the internals of the system. Black Box testers do not have access to the source code and are oblivious to the system architecture. A Black Box tester typically interacts with a system through a user interface by providing inputs and examining outputs without knowing where and how the inputs were operated upon. In Black Box testing, the target software is exercised over a range of inputs and the outputs are observed for correctness. Advantagesa. Efficient Testing — Well suited and efficient for large code segments Read More


So far we’ve worked with a natural thought of what testing is. we’ve perceived that it’s a movement wont to diminish chance and improve quality by discovering surrenders, which is all evident. In any case, we’d like to grasp somewhat more about how programming testing functions by and by before we will consider the way to execute powerful testing. Testing and debuggingTesting and debugging are different sorts of activities, both of which are vital. Debugging is that the process that developers undergo to spot the explanation for bugs or defects in code and undertake corrections. Ideally, some check of the correction is formed, but this might not reach checking that other areas of the system Read More

Interview Question of fundamentals of testing

Interview Question of fundamentals of testing, Q1. Which of the following is correct?, Which of the following are aids to good communication, and which hinder it?, Which option is part of the ‘implementation and execution’ area of the fundamental test process?, The five parts of the fundamental test process have a broad chronological order. Which of the options gives three different parts in the correct order?, Which pair of definitions is correct?, Which statement is most true?, When is testing complete?, Which list of levels of tester independence is in the correct order, starting with the most independent first?, The following statements relate to activities that are part of the fundamental test process. , Which of the following describes why testing is necessary?, Which one of the following definition pairs is correct?, How does software testing lead to higher quality?

Why is software testing needed?

This information is useful whether you are a software engineer who needs to test your own software, a full-time tester who works generally from prerequisites at the client level, a director accountable for testing or advancement, or any position in the middle. As the software business moves in the twenty-first year of the twenty-first century, software quality is progressively turning out to be vital for all organizations, and information on software testing is turning out to be fundamental for all software engineers.     Today, software defines behaviors that depend on our civilization, for example, online cab, bus, train tickets & flight Read More

Manual Testing Questions and Answers

  1. What is Acceptance Testing? Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.   2. What is Accessibility Testing? Verifying a product is accessible to people having disabilities (deaf, blind, mentally disabled, etc.).   3. What is Ad Hoc Testing? A testing phase where the tester tries to ‘break’ the system by randomly trying the system’s functionality. Can include negative testing as well. See also Monkey Testing.   4. What is Agile Testing? Testing practice for projects using agile methodologies, Read More

Top-Down Integration Testing

An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower-level components being simulated by stubs. Tested components are then used to test lower-level components. The process is repeated until the lowest level components have been tested.   In this approach, testing is conducted from the main module to the submodule. if the submodule is not developed a temporary program called STUB is used for simulating the submodule.   Advantages: * Advantageous if major flaws occur toward the top of the program. * Once the I/O functions are added, the representation Read More

Bottom Up Integration Testing

An approach to integration testing where the lowest level components are tested first then used to facilitate the testing of higher-level components. The process is repeated until the component at the top of the hierarchy is tested. In this approach, testing is conducted from the submodule to the main module, if the main module is not developed a temporary program called DRIVERS is used to simulate the main module. Advantages: * Advantageous if major flaws occur toward the bottom of the program. * Test conditions are easier to create. * Observation of test results is easier. Disadvantages: * Driver Modules Read More