Frequently asked questions when going for Tester interviews

> Frequently Asked Questions When Interviewing Testers 1. What is Static testing? • Tested at an early stage, when we only have the requirements and design documents but have not yet written or executed the code, dynamic testing is not feasible, it requires reviewing the requirements. requirements and specification to test logic without running the program 2. What is dynamic testing? • Testing is done after the code is available, and has been built. Use the program runner to check the operating status of the program • Test against test cases determined by the execution of the test object • Input input and output values ​​to check the results desired result 3. Black box? • Test data is obtained from specifications such as: Equivalence Classifier, Boundary Value, Model Based, Trace Matrix, Probe, Specification, … • Not related to code, this is an objective assessment. Is exploration blind because do not know how the software is built 4. White box? • Survey the internal structure. We will access data structures and algorithms inside the program, including: API Interface, Command Coverage, Error Assignment, Conversion, Static. • Used to evaluate the completion of software created with the black box method 5. Gray box? • Access to data structures and internal algorithms but can only be checked at the user or black box level, the manipulation of input and output data is not clear 6. How to write Test cases that can cover all request? • When testing we should compare back and forth between the screen and the test case. Based on the equivalence region, boundary value estimation, pairwise (combining test conditions), error guessing, and experience. • If the requirement to handle is too complicated, then we should draw the Flow chart of the requirement, then follow each branch and write test cases to investigate the test cases. As for the relative screens, there is no need to draw a flow chart, but write test cases in the order of the interface (GUI) to validate for each item, then the function of each button (add, delete, edit, cancel, search…) 7. What is Performance Testing? => Performance testing is generally a type of testing with the intention of determining the responsiveness, throughput, reliability and/or scalability of a given system of workloads. 8. Explain the types of testing: Stress Testing, Load Testing – Load testing to check the application’s ability to handle under normal load conditions or maximum load conditions. Stress testing: Focuses on defining or testing the performance characteristics of the system or application under test under conditions that are beyond those anticipated in product operations. Products. It involves tests that go beyond the normal capabilities of the system. -> various: + Load: normal condition + Stress: exceeds its load capacity. 9. The system has the following features: Login, Register, View Products, Purchase… TH1: User 1 completes the above functions, will go to User 2, similarly, User 2 is done, will come to User 3, the Users will perform sequentially… TH2: n Users will access the system together and at the same time will perform the above functions. Ask for the processing speed and responsiveness of the Server in 2 fields. What is the above case? Same or different, and if different, how? 10. How does JMeter test performance on mobile? Jmeter is used to test the performance of the server, so you only need to simulate the dc request, then the config is testable (regardless of mobile or webpage) 11. Besides jmeter, what other tools do you use to compare that tool with jmeter. why i use jmeter to test my game performance without using other => Jmeter, Appload, Loadrunner. 12. What is the difference between automated regression testing tools and automated performance testing tools? – Automated testing tools: record test operations and re-execute them after a certain point in time. Record and re-execute functionality is the essence of regression testing. – Performance testing tool: determine the load a server can handle. And the must-have function is to make multiple Users run on the same machine, schedule and synchronize other users, can measure the network load – network load – when there are many simulated users accessing 13. ODBC is what? Open Database Connectivity (ODBC) is an open standard application-programming interface (API) that allows access to Databases. ODBC is based on Structured Query Language (SQL) with Call-Level communication. It allows programs that use SQL to query the database directly without having to know the personal interfaces – proprietary interfaces – to the database. ODBC uses SQL queries and transforms them into queries that are understood by the individual database system. 14. Exception Testing is not Exploratory Testing In my opinion, exception testing is testing cases related to the system’s errors, maybe testing whether the system (software, application, …) handles it. like when the server is down, or the Database server is not working, timeout, lost connection while processing, … or system crashes due to input data not correct with expected data type. I think Exception Testing is more like Recovery Testing 15. Is it possible to test all cases? No, Because sometimes errors happen endlessly, sometimes some cases only happen once 16. If tested, there will be no bugs? No one can guarantee or guarantee that the application is 100% free of bugs 17. Testers only have 1 job to find bugs? Finding bugs is the task of a tester, but also an expert of a software because it is necessary to understand the entire operation of the PM and what is the relationship? influence of other modules. Sometimes testers have to analyze requirements and come up with a solution to the problem 18. When is testing automation? – When the project is large and long-term. 1 program (pm) has the same requirements, little change in the future, is stable and can be tested by hand – Test cases need to be performed many times, often need to perform regression testing, a number of Large test data needs to be completed in a short time. – Testing that needs to be performed in different environments – Testing basic operations that have to be repeated with large amounts of test data – Testing multiple screens in a short, continuous time – Executing performance or load tests test, then automated testing is almost the only option 19. What is the plus point of a tester? Knows many different business domains, looks deeply into the whole system, can look at a problem from many angles, can handle situations well 20. What skills are required of a tester? Analytical ability, fast learning, meticulous, communication, English and can support team 21. Order when testing web? – Pagination by top, buttom, right, left, test treebn each area – Top: the header has many menus – Each menu: has many functions – Function: there will be many orders, add, edit, delete…. – Test environment: browser, flow, resize, zoom, tooltip, highlight, tab, font, function… 22. Why did you change companies? Good old company, but now want to join an environment… (tell the good points of the company you are working on), want to learn more…. 23. What kind of environment would you like to work in? (Should consult trupocws company when interviewing) 24. Performing test is doing but what? Read specification document -> Design test plan -> Create test case -> execute test -> post bugs -> report bugs 25. Test says bug but Dev says no, what will you do? Check all the environment and conditions required to generate bugs (such as browser, configuration …), return to the demo screen or can demo directly to the dev to see, if Dev still does not accept that it is bugs, then check Check the cause of those bugs. If Dev still refuses, you can ask your colleagues first, then report to your superiors and note the bug 26. Your strengths and weaknesses – Strengths: Ability to analyze, learn, observe and create. take a stance – Weak: Or focus on one problem, so it causes too much time, too many small mistakes, too perfectionist 27. What will you contribute to our company? I will help your company create quality software with the least errors. and will contribute to the development of the company 28. If you are accepted, when will you be able to work? Should answer no more than 1 month 29. Your desired salary Should deal straight. does not cover, or about 30. Future goals and plans to achieve ? Want to develop your current position to a higher level, want to become a test expert within … years from now 31. What did your previous manager say about you? Honest, highly logical. Or critique to find out many cases 32. What problem do you find the biggest and most difficult when participating in KTPM? Terms. Because when entering a new job, learning to understand the software is also an obstacle. 33. How do you organize your workload? Arrange the appropriate time for each task, what tasks need to be handled in the day, the importance and necessity of a task 34. Pros and cons of a tester? Pros: Learn many technologies, many programs, many professions to create a good program for users. Weak: Find errors and retest 1 error many times causing boredom 35. The main goal of test plan is what? Plan to analyze and design appropriate time, tasks, and personnel, In order to save time, personnel and finance 36. When should test execution be done? Test should be executed at all test level 37. What is the difference between regression test and retest? – Re-testing means re-testing the functionality or bugs to make sure the bug has been fixed. Regression testing means testing a software application when it undergoes a code change to ensure that the new code changed does not affect other parts of the software. 38. What is the difference between beta test and alpha test? (more information can be found online) – Beta testing aims to provide information from real user feedback. – Alpha testing helps you simulate the real environment to test the software before going to the Beta testing process. Alpha and Beta testing are integral to the software development lifecycle. 39. how many test levels and test types? https://blog.haposoft.com/kiem-thu-phan-mem-cac-loai…/ 40. What is Negative Testing? Testing is aimed at making the software not work. This is also called “test to fail” 41. What is Positive Testing? Tests are intended to show the software in action. This is also called “test to pass”. 42. What is Stress Testing? Testing conducted to evaluate a system or component at or beyond the limits of its specific requirements to determine the load at which it fails and how. Usually this is performance testing using a very high degree of simulation 43. What does a test plan include 44. What is the testing process from request receipt to completion? 45. Can auto test replace manual test, when should auto test be used 46. What if the deadline is not in time to fully test the system? 47. What if there are too many bugs that can’t be fixed by the deadline? 48. What if I have to request a system test without any documentation? 49. For example, a function on mobile (2 people are calling like skype for example), what are the exception cases? 50 What are the advantages/disadvantages of the agile model? when to use agile? QC role in agile? 51. What is Exploratory testing? Self-search 52. What is an ad-hoc test? Self-search 53. What components should be included in the test case? 54. What is jmeter? 55. Does jmeter support mobile application testing? 56. How to make sure the test case covers the requirement 57. Learn about end to end testing 58. API testing, tool used to test, write api testcase 59. Upload an image file (requirement is to allow uploading 1 image below 7 bytes) list out test case for it 60. Given 1 If else, draw the flow corresponding to the result (if width > height -> biggest dimension = width else …) 61. Knowledge of scrum? procedure? – when applying Scrum, there are 4 important meetings (Meetings or Ceremonies) that make up the structure in each Sprint as follows: + Sprint planning: A planning meeting of the project team, to determine what needs to be done in the Sprint. Spring is coming. + Daily stand-up: Also known as “Daily Scrum”, a small meeting every 15 minutes to exchange work between the development team. + Sprint demo: A sharing meeting, where members point out what they have done in that Sprint What can be done by the current Sprint, and give action solutions for the next Sprint to be better and more complete http://ecci.com.vn/qui-trinh-scrum-la-gi 62. How to retest bugs like that any? Test case is described in bug, if pass then test them ad-hoc around 63. How to write test case effectively? – Understand the feature of the Feature I am writing Test (if it is a function test) Then I have to separate the TC writing in 2 directions: – UI/UX: + Aligment + Color + Easy to use…. – Function + Coi What features does it include, list it out, then go into each case (positive case first) + Then pay attention to the abnormal cases like: 1 userA is Editing, User B Delete the same record, User A is Editing, User A remove permission User A on record… etc 64. How to review test cases written by others? – Regarding the review, I also have to go from general to detailed like when I write test cases – When reviewing, we need to pay more attention to whether the Test case is in a reasonable Testing Level 65. Introduction about the project we’re working on, what do you do? in du An do? 66. How to solve the problem when there is a conflict with the dev? 67. How is the sytem test different from the interation test? What do you do at the sytem test stage? 68. for 1 screen seach. Please list possible test cases? 69. What is Database testing Database Testing is the process of checking the accuracy and integrity of a database (database). Ensure that the data is accurate and unique. The following database errors can cause some serious problems: deadlock, data corruption, poor performance, inconsistency, etc. 70. List 5 basic testing techniques. In that transition state test how? Boundary Value Analysis (BVA): tests at the boundaries between partitions, including maximum, minimum, inner or outer boundaries. If an input condition is limited between x and y values, then the test cases must be designed with x and y values ​​as well as values ​​above and below x and y. – Equivalence Class Partitioning: allows dividing the set of test conditions into a partition that is considered to be the same. allows to define valid as well as invalid equivalence classes. Decision Table based testing: used for functions that respond to combinations of event inputs. The first is to define functions where the output depends on a combination of inputs – State Transition: This method is used when the system has a process to change from this state to another state after a specific action. Changes in input conditions will change the state of the Application Under Test (AUT). The tester will perform the action of entering various input conditions in sequence, which may be valid. valid and valid for system processing evaluation. There are two ways to represent it: – In the state transition diagram, the states are shown in framed text and the transition is shown by arrows. – In the state transition table, all states are listed on the left side and events are described at the top. The main advantage of this testing technique is that it will provide a graphical or tabular representation of how the system behaves, which will help the tester to effectively cover and understand how the system behaves. The main disadvantage of this testing technique is that we cannot rely on it all the time. – Error Guessing: This is a technique based on experience, understanding of the system, .. 71. What do people do in the sytem test phase? System Test is mainly Test of accuracy in many data centers. different (ma san pham ho tro) Test scenarios di tu Deploy app, And main test cases of the whole project. It is necessary to ensure that the operation of the software is a unified block. It should be checked that the product does not bypass any functional as well as non-functional requirements. Product testing should be performed on the same environment as the actual product. It is necessary to perform product testing with the same data as the actual product data. This is the first step to testing the application on a fully integrated complete software product before it is released. 72. how to write test cases? – Test Cases need to be simple and transparent: Make Test Cases as simple as possible. Test Cases should be clear and concise as the author of Test Cases may not execute them. Use easy to understand language like: go to home page, enter data, click Submit… This makes understanding test steps easier and test execution faster. – Create Test Cases as end users – Avoid repeating Test Cases. – No guesswork – 100% coverage guaranteed – Test Cases must be defined. – Implement testing techniques + Boundary Value Analysis (BVA) + Equivalence Partition (EP) + State Transition Technique + Error prediction technique Guessing Technique) – Clean up the test environment: This is especially true for configuration testing. – Tescase must correspond to each test level -. Reviews of colleagues. review testcase 73. ask about auto test: API, posman tool, elements to create a website, experience with DB and code at what level? 74. Difference between Smoke test and Sanity test? 75. What’s the difference between a web app and a mobile app? When testing hybrid apps (offline webapps), what should be tested? 76. What does POM (auto test) help with testing? 77. Why choose testing as career path? 78. What is Test localize and internationlize? 79. What techniques are used in testing? 80. What is API testing? What is the essence of API testing and how does it help in testing? 81. What is my daily task? 82. Description of acitivities in Scrum model 83. When running regression, choose regression sets? Is there anything in choosing TCs to run regression, smoke test… k? And will run ntn? 84. What is black box testing?

Source : Viblo