Why and When Selenium is selected for testing? Dipali Kalaskar Apr 16th, Selenium is open source tool so no need to invest for testing on this tool. May 18 AM. Stable Browser for Selenium akhilandeswari Profile Answers by akhilandeswari Questions by akhilandeswari. Which browser version is stable for Selenium? Rajeswari May 30th, Mozilla Firefox Anda May 23rd, FireFox. Apr 07 PM. Dipali Kalaskar Apr 16th, Agile is the mindset. How to move one selenium sit to other sit? Answer Question. Jan 22 PM.
What is the difference between agile model , vmodel and fish model? Nov 20 AM. Retesting a Defect boinapally Profile Answers by boinapally Questions by boinapally. Apr 30 AM. Can we delete unattached folder in Test plan quality center ashish Jun 3rd, Yes May 16 AM.
GV Jan 21st, Wait 10 wait for 10milli seconds. Place cursor at respective position and press F9 Breakpoint. Aug 20 AM. What do you mean by Progression Testing? Samuel Sep 10th, The word progression test also seems to be a false translation from German.
Jun 19 PM. Thanks,Abhi bhargavi vittalsingh Profile Answers by bhargavi vittalsingh Questions by bhargavi vittalsingh. Enterprise Web Test is open source function testing tool.
Showing Questions 1 - 20 of 67 Questions. Open Questions Answered. Latest News. It looks like you are using an AD Blocker! Disable Ad Blocker Learn More. Login GeekInterview Login. Create your GeekInterview account Signup. Continue Reading after Disabling Refresh. Identifying all the possible areas to be tested or what is to be tested is termed so. It is a method for deriving test cases. What is a Defect? Any flaw or imperfection in a software work product is termed as a Defect.
What is Severity? It defines the importance of the defect from the functional point of view i. What is Priority? It indicates the importance or urgency of fixing a defect. What is Re-Testing? Re-testing the application means verifying whether the defects have been fixed or not.
What is Regression Testing? Verifying an existing functional and non-functional area after making changes to the part of a software or addition of new features is termed so. What is Recovery Testing? Checking whether the system is able to handle some unexpected or unpredictable situations is called Recovery Testing.
What is Globalization Testing? It is the process of verifying whether software can be run independently of its geographical and cultural environment. Checking if the application is having features of setting and changing language, date, format, and currency if it is designed for global users.
What is Localization Testing? Verifying globalized application for a particular locality of users, under cultural and geographical conditions is termed so. What is Installation Testing? Checking whether we are able to install a software successfully or not, as per the guidelines given in the installation document is called Installation Testing.
What is Un-Installation Testing? Checking whether we are able to uninstall the software from the system successfully or not is called Un-Installation Testing. What is Compatibility Testing? Checking whether the application is compatible with different software and hardware environment or not is called Compatibility Testing. What is a Test Strategy? It is a part of a test plan describing how testing is carried out for the project and what testing types need to be performed on the application.
What is a Test Case? A Test case is a set of pre-conditional steps to be followed with input data and expected behavior to validate the functionality of a system. What is Business Validation Test Case? A test case which is prepared to check the business condition or a business requirement is called Business Validation test case.
What is a Good Test Case? A Test case that has the high priority of catching defects is called a Good Test Case. What is Use Case Testing? Validating a software to confirm whether it is developed as per the use cases or not is called Use Case testing. What is a Defect Age? What is Showstopper Defect? A defect which is not permitting to continue further with testing is called Showstopper Defect. What is a Test Closure? It is the last phase of the STLC, where the management prepares various test summary reports that explain the complete statistics of the project based on the testing carried out.
What is Bucket Testing? It is mostly used to study the impact of various product designs in the website metrics. Two simultaneous versions are run on a single or a set of web pages to measure the difference in click rates, interface, and traffic. What is Concurrency Testing? This is a multiple user testing to access the application at the same time to verify the effect on code, module or DB and it is mainly used to identify the locking and deadlocking situations in the code.
What is Web Application Testing? Web application testing is done on a website to check — load, performance, security, Functionality, Interface, Compatibility and other usability-related issues. What is Unit Testing? Unit testing is done to check whether the individual modules of the source code are working properly or not. What is Interface Testing? Interface testing is done to check whether the individual modules are communicating properly as per the specifications or not. Interface testing is mostly used to test the user interface of GUI applications.
What is Gamma Testing? Gamma testing is done when the software is ready for release with the specified requirements, this testing is done directly by skipping all the in-house testing activities. What is the Test Harness? Test Harness is configuring a set of tools and test data to test an application under various conditions, which involves monitoring the output with the expected output for correctness. The benefits of Testing Harness are : Productivity increase due to process automation and increase in the product quality.
What is Scalability Testing? It is used to check whether the functionality and performance of a system are capable to meet the volume and size changes as per the requirements. Scalability testing is done using load test by changing various software, hardware configurations, and testing environment. What is Fuzz Testing?
Fuzz testing is a black box testing technique which uses random bad data to attack a program to check if anything breaks in the application. It is process oriented and its Aim is to prevent the defects in an application. QC is product oriented and it is a Set of activities used to evaluate a developed work product. Executing and verifying an application with the intention of finding defects.
What is Date Driven Testing? It is an Automation testing process in which an application is tested with multiple sets of data with different preconditions as an input to the script. I'm sure that with a thorough knowledge of these Questions and Answers, you can appear for any QA Testing Interview confidently and get through very successfully. The questions will emphasize more on the quality processes and the strategy, so please see that the question will not be asked for Testing.
Quality Assurance is the process of planning and defining the way of monitoring and implementing the quality test processes within a team and organization. This method basically defines and sets the quality standards of the projects. Quality Control is the process of finding defects and providing suggestions to improve the quality of the software.
The methods used by Quality Control are usually established by the quality assurance. It validates whether the software built by the development team meets the requirements set by the user and the standards set by the organization. QA activity should start from the beginning of the project. The more early it starts the more benefit it is to set the standards for achieving the quality. Test Strategy is at a higher level, mostly created by the Project Manager which demonstrates the overall approach of the testing for the entire project, whereas Test plan basically depicts the how the testing should be performed for a particular application, falling under a project.
Software Testing Life Cycle refers to a testing process which has specific steps to be executed in a definite sequence to ensure that the quality goals have been met. In simple words, a good test case is one which finds a defect. But all test case will not find defects, so A good test case can also be one which has all the prescribed details and coverage.
Q 7 What would you do if you have a large suite to execute in very less time? In case we have less time and have to execute larger volume of test cases, we should prioritize the test case at first instant and execute the high priority test cases first and then move on to the lower priority ones.
Alternatively, we may also seek customer preference that which is the most important functionality of the software according to them, and we should start testing from those areas and then gradually move to those areas which are of less importance.
Q 8 Do you think QA's can also participate to resolve production issues? It would be a good learning curve for QA's to participate in resolving production issues.
Many a time production issues could be resolved by clearing the logs or making some registry settings or by restarting the services.
Also If QAs have an insight on resolving the production issues, they may also include them while writing the test cases, and this way they can contribute to improve quality and try to minimize the production defects. Q 9 Suppose you find a bug in production, how would you make sure that the same bug is not introduced again?
The best way is to immediately write a test case for the production defect and include it in the regression suite. This way we ensure that the bug does not get introduced again. Also many a time we can also think of alternate test cases or similar kind of test case and include them in our planned execution.
Q 10 What is the difference between functional and nonfunctional testing? Functional testing basically deals with the functional aspect of the application. We take conditions as inputs and actions as outputs. Using state transition testing, we pick test cases from an application where we need to test different system transitions.
We can apply this when an application gives a different output for the same input, depending on what has happened in the earlier state. The prerequisites that must be achieved before commencing the testing process. The conditions that must be met before testing should be concluded.
Software Development Life Cycle SDLC aims to produce a high-quality system that meets or exceeds customer expectations, works effectively and efficiently in the current and planned information technology infrastructure, and is inexpensive to maintain and cost-effective to enhance. We can do System Testing only when all the units are in place and working properly.
Manual testing is crucial for testing software applications more thoroughly. The procedure of manual testing comprises of the following. Planning and Control 2. Analysis and Design 3. Implementation and Execution 4. Evaluating and Reporting 5. Test Closure activities.
Even though testing differs between Organizations, there is a testing life cycle. Requirements Traceability Matrix RTM is used to trace the requirements to the tests that are needed to verify whether the requirements are fulfilled. We have to ensure that every requirement has atleast 1 test case. Software test metrics is to monitor and control process and product.
It helps to drive the project towards our planned goals without deviation. Metrics answer different questions. API testing is a type of software testing that involves testing APIs directly and also as a part of integration testing to check whether the API meets expectations in terms of functionality, reliability, performance, and security of an application.
Prerequisites to start writing black-box test cases are Requirement documents or design documents. These documents will be available before initiating a project. Prerequisites to start writing white box test cases are the internal architecture of the application. The internal architecture of the application will be available in the later part of the project i. Workbench is a practice of documenting how a specific activity must be performed.
It is often referred to as phases, steps, and tasks. In random testing is a form of black-box software testing technique where the application is testing by generating random data. After reading this Interview Questions for Manual Testing, if you find that we missed some important questions, please comment below we would try to include those with answers.
Here I have hand-picked a few posts which will help you to learn more interview related stuff along with these interview questions on manual testing. If you have any more manual interview questions, feel free to ask via comments. If you find this post useful, do share it with your friends on Social Networking.
He has extensive experience in the field of Software Testing. Furthermore, he loves to be with his wife and a cute little kid 'Freedom'. Sure Shahi… we will do it. Could you please explain : 1.
Testing process.. Challenges — for examples repeated testing which we overcome using automation tool 3. Bug life cycle is almost same in all the tools.. Raj Kumar you have done a great job. You have covered every single topic from Manual Testing syllabus.. Your answer was right, but you need to give them the right logic as below: If HDFC net banking website Bank name is misspelled then it may leads to ward the doubt that the site is not authentic and we cant risk with login.
It may expose the login credentials to the frauds. So i will not take risk and avoid login to the portal. Hi, I have read your Manual Testing Materials. It looks like very helpful for the job seeker for preparing interview. Thanks for helping out people by providing such a quality document. Good Work.. Hoping for some new tutorials on Tosca, UFT etc. I liked your blog and its have excellent information about Software testing. Keep up the good work.
Hi Sourabh, thanks. We will surely look into that. If you feel anything very important is not covered here, please share it in the comment section and we will include them in this Manual Testing Interview Questions blog post. Your email address will not be published. Skip to content. Like This Post? Subscribe and get free access to subscriber-only guides, templates, and checklists. Yes, I'm In! You are subscribing to email updates.
Unsubscribe anytime. Your data is safe. Post navigation Previous Previous. Next Continue. Similar Posts. Hi Sir, I went through your manual testing tutorial its very good and easy to understand thanks a lot.
Nice information. Hello Sir, Your explanation was clear and easy to ready and easy way to explain login Thank you so much Sir, Could you please explain : 1. Thank you. Hi Saravani, Your answer was right, but you need to give them the right logic as below: If HDFC net banking website Bank name is misspelled then it may leads to ward the doubt that the site is not authentic and we cant risk with login.
Hi Rajkumar, I liked your blog and its have excellent information about Software testing. Thanks, Amit. Thanks Amit. Please share about this blog with your friends too. Grt Aticle Rajkumar, Experience holder can revision Fresher can read and understand the basic testing concept. Leave a Reply Cancel reply Your email address will not be published.
Blog Tutorials Expand child menu Expand. Tools Expand child menu Expand. Quiz Expand child menu Expand. Toggle Menu Close. Search for: Search. Test Engineer thinks only in the terms of pass or fail of a test case and how to break the software.
Test Engineer works only for test life cycle, like design of test cases, and execution. Dynamic skill sets, like knowledge of quality and testing and good in coding too. Test Engineers know where repetitive work or simple data entry is present but they are not expected to minimize the repetitive tasks.
SDET understands automation needs, they can code and provide a solution to the team where repetitive kind of work is killing the time. They can design framework which can help testing team to reduce repetitive test cycle or simple data entry task. Test Engineers are not expected to reach up to code level and tune the performance. Well aware of Performance tuning and security threats , they can suggest and reach to the code and suggest where application is poor in performance, plus they can optimize the code.
Developers are only expected to code the functionality which is expected by customer. Testers perform both functional as well as non-functional testing to evaluate the functionality, usability, performance testing etc.
The difference between a pilot and beta testing is that pilot testing is actually done using the product by the group of users before the final deployment, and in beta testing, we do not input real data, but it is installed at the end customer to validate if the product can be used in production. Testing technique: — Is a process for ensuring that some aspects of the application system or unit functions properly there may be few techniques but many tools. Testing Tools: — Is a vehicle for performing a test process.
The tool is a resource to the tester, but itself is insufficient to conduct testing. Learn More About Testing Tools here. Component testing, also known as unit, module, and program testing, searches for defects in and verifies the functioning of software e.
Component testing may be done in isolation from the rest of the system depending on the context of the development life cycle and the system. Most often stubs and drivers are used to replace the missing software and simulate the interface between the software components simply. A stub is called from the software component to be tested; a driver calls a component to be tested. Here is an awesome video on Unit Testing.
Testing the end to end functionality of the system as a whole is defined as a functional system testing. Random testing is often known as monkey testing. In such type of testing data is generated randomly often using a tool or automated mechanism. With this randomly generated input, the system is tested, and results are analyzed accordingly.
These testing are less reliable; hence it is normally used by the beginners and to see whether the system will hold up under adverse effects. In contrast to informal reviews, formal reviews follow a formal process.
A typical formal review process consists of six main steps:. The moderator or review leader leads the review process. He or she determines, in co-operation with the author, the type of review, approach and the composition of the review team. The moderator performs the entry check and the follow-up on the rework, in order to control the quality of the input and output of the review process.
The moderator also schedules the meeting, disseminates documents before the meeting, coaches other team members, paces the meeting, leads possible discussions and stores the data that is collected. Learn More about Review process in Video Tutorial here. Structure-based testing techniques which are also dynamic rather than static use the internal structure of the software to derive test cases. For example, a structural technique may be concerned with exercising loops in the software.
Different test cases may be derived to exercise the loop once, twice, and many times. This may be done regardless of the functionality of the software.
After the software has changed or when the environment has changed Regression testing should be performed. A negative test is when you put in an invalid input and receives errors. While positive testing is when you put in a valid input and expect some action to be completed in accordance with the specification. Re-testing ensures the original fault has been removed; regression testing looks for unexpected side effects. The experience of both technical and business people is important, as they bring different perspectives to the test analysis and design process.
Due to previous experience with similar systems, they may have insights into what could go wrong, which is very useful for testing.
It depends on the risks for the system being tested. There are some criteria based on which you can stop testing. The primary purpose of the integration strategy is to specify which modules to combine when and how many at once.
Semi-random test cases are nothing, but when we perform random test cases and do equivalence partitioning to those test cases, it removes redundant test cases, thus giving us semi-random test cases.
Regression testing should be done on other modules as well because fixing one module may affect other modules. Because configuration management assures that we know the exact version of the testware and the test object. A software development model that illustrates how testing activities integrate with software development phases.
0コメント