This will help newcomers to the industry, as well as testing professionals who want to switch jobs!!
First, you need to know about software testing!
The first basic thing – testing concepts: You need to be very good at this, especially manual testing methods. But knowing the different test concepts is only half the job. Next – the most important thing is to know which type/technique/concept of testing can be applied at which stages of the SDLC.
“What should I test, and when should I start testing?” Very important. There may be concepts that do not apply to our company’s professional testing, but are always better at helping us understand all testing practices.
Many newcomers and testing professionals may not work in various testing areas, such as localization testing, time zone testing, etc. But knowing more about what you do will help you better answer the interviewer’s different questions.
In addition to my current project work, I always try to keep my testing knowledge up to date. This helped me a lot when I switched jobs a few years ago.
What if an interviewer asks you a question about a topic you’ve never worked on? For example, suppose you don’t have any experience testing web-based projects or client servers, but the interviewer asks you to test the Yahoo Mail application. Can you answer this question?
You can be. Even if you haven’t worked on any of these projects. So how do we do that? In this case, your curiosity about learning something you’ve never done before can help. So broaden your mind and be curious about every job and every problem you face in your daily work.
Learning more doesn’t hurt and will certainly help you at least contribute your own ideas to the interviewer’s questions.
What’s the difference between references and Pointers?
- A reference must be initialized, not a pointer.
- A reference cannot be changed after initialization, and a pointer can change the object to which it refers.
- There are no references to null values, but there are Pointers to null values.
What network protocol is used? What are the main hierarchies of the protocol? Internet. Physical addresses and IP addresses. What protocol does address translation use?
The TCP/IP protocol has the following layers: application layer, transport layer, network layer, and digital link layer.
Address Resolution Protocol (ARP)
Describe your understanding of the top-down and bottom-up integration strategies in integration testing. Discuss their strengths and weaknesses and which types of testing are best suited to them
1. Top-down integration
Advantages: Early validation of key control and judgment points; Depth-first can realize and verify a complete software function first; Function early confirmation, bring confidence; Only need one drive, reduce the cost of driver development; Supports fault isolation.
Disadvantages: large amount of column development; Underlying validation is delayed; The underlying components are not tested adequately.
Adapt to the product control structure is clear and stable; The change of high-level interfaces is small; The underlying interface is undefined or often subject to modification; Production control components have a high technical risk and need to be verified as soon as possible; We hope to see the system functional behavior of the product as soon as possible.
2. Bottom-up integration
Advantages: Early validation of underlying component behavior; Work can initially be integrated in parallel, which is more efficient than top-down; Reduced pile workload; Supports fault isolation.
Disadvantages: driver development workload is large; Verification at the top was delayed, and design errors could not be discovered in time.
Adapt to the bottom interface is relatively stable; High-level interfaces change frequently. The underlying components are completed earlier.
There are many kinds of system testing strategies, including performance testing, load testing, strength testing, usability testing, security testing, configuration testing, installation testing, documentation testing, failure recovery testing, user interface testing, recovery testing, distribution testing, availability testing.
The project documents you need to refer to to design a system test plan are software test plans, software requirements artifacts, and iteration plans
The procedure for writing test cases by drawing causal diagrams is…. And a total of five steps to transform a causal diagram into a state diagram.
The basic steps for generating test cases from cause-and-effect diagrams are:
§ Analyze the software specification description, which are causes (i.e. input conditions or equivalent classes of input conditions) and which are effects (i.e. output conditions), and assign an identifier to each cause and effect.
§ Analyze the semantics in the software specification description to find the relationship between cause and effect. What is the corresponding relationship between cause and cause? From these relationships, draw a causal diagram.
§ Some combinations of cause to cause and cause to effect are impossible due to grammatical or environmental constraints. To indicate these special cases, constraints or constraints are marked on causal diagrams. § Convert causal diagrams into decision tables.
§ Design test cases based on each column of the decision sheet.
Please say who is the best person to do these tests, and what are they?
Code – and function-level testing is usually done by white-box testers, who check the correctness of each piece of code or function to see whether it correctly implements specified functions.
Module and component level testing is mainly based on the program structure to design the integration and call relationship between test modules, which is generally completed by testers.
System testing is based on module testing and unit testing. Understand system function and performance, conduct comprehensive test according to test case.
What aspects should be considered when designing test cases, that is, for which aspects should different test cases be tested?
When designing test cases, attention should be paid to strength test, performance test, pressure test, boundary value test, stability test, security test and other aspects in addition to the overall process and function.
(The four basic elements to consider in a test case are input, output, operation, and test environment; In addition, test cases need to consider the type of test (function, performance, security…) , this part can be answered by referring to TP. Also consider the importance and priority of use cases.)
When you save a text file in Windows., the save dialog box will pop up. If you create test cases for file names, how should the equivalence classes be divided?
A single byte, such as A; Double bytes, AA, I, I; Special characters/’. ‘; , = – etc. Reserved words, such as com; The file format is 8.3; The file name format is not 8.3; Nine special characters, including /,, and *.
Suppose you have a text box that asks for a 10-character zip code, how do you classify equivalence classes for that text box?
Special characters, such as 10 * or ￥; English letters, such as ABCDefghik; Less than 10 characters, such as 123. More than 10 characters, for example, 11111111111. Mixing numbers with others, such as 123AAAAAAA; Null character; Reserved characters
When did the software testing program begin? Why is that?
Software testing should start at the requirements analysis stage, because testing is not just about coding, but all products produced during software development, and software defects tend to be amplified. The later a defect is discovered, the more it will cost to fix it.
What is regression testing?
Regression testing has two types: use case regression and error regression; Use case regression is going back in time and re-testing the use cases that have been used before to see if they rediscover the problem.
Error regression is a method to verify the defects that appeared and repaired in the previous version again in the new version and test the modified parts with the defects as the core.
What is the focus of unit testing, integration testing, and system testing? Unit test is aimed at the smallest unit of software design — program module (oriented to process is function, process; In object orientation, classes.) , the test of correctness check is to find the possible errors within each program module. Generally, there are two steps: manual static check dynamic execution tracking integration test is aimed at the components integrated by each module through the unit test, its main content is the interface between each unit module, as well as the functions realized by each module integration. System test is aimed at the integrated software system, as an element of the whole computer system, and computer hardware, peripherals, some supporting software, data and personnel and other system elements together, in the actual operating environment, to the computer system for a series of integration tests and confirmation tests.
What qualities should a test engineer have?
1. Sense of responsibility
2. Communication skills
3. Team work spirit
Patience, carefulness and confidence
5. Always be skeptical and have a sense of defect prevention
6. Have some programming experience
What are the types of software testing that you know about?
By test strategy:
1. Static and dynamic testing
2, black box and white box test
3. Manual and automatic testing
4. Smoke test
5. Regression test;
Classification by test stage: unit test, integration test, system test;
Other common test methods:
1. Functional testing
2. Performance test
3. Stress test
4. Load test
5. Usability testing
6, installation test
7. Interface testing
8. Configure tests
9. Document testing
10. Compatibility testing
11. Security testing
12. Recovery tests
What do you think is the key to good test planning?
Clarify the objectives of the test and make the test plan more practical
An important purpose of writing a software test plan is to enable the testing process to discover more software defects, so the value of a software test plan depends on its ability to help manage the test project and identify potential software defects.
Therefore, the test scope in the software test plan must highly cover the functional requirements, the test method must be feasible, the test tool must be highly practical, easy to use, and the generated test results are intuitive and accurate
Adhere to the “5W” rule, clear content and process
The 5W rule refers to “What,” “Why,” “When,” “Where,” and “How.” Create a software test plan using the “5W” rule,
It can help the test team understand the purpose of the test (Why), clarify the scope and content of the test (What), determine the start and end dates of the test (When), indicate the methods and tools of the test (How), and give the location of the test documents and software (Where).
Use review and update mechanisms to ensure that test plans meet actual requirements
If the test plan is directly sent to the test team without review after completion, the test plan content may be inaccurate or missing test content, or the test scope may be increased or decreased due to software requirements change, and the test plan content is not updated in time, misleading the test executive.
Create test plans and test specifications and test cases respectively
Detailed test technical specifications should be included in a independently created test detail specification document, and test cases used to guide the test team in executing the test process should be placed in a independently created test case document or test case management database.
The relationship between test plan, test specifications and test cases is strategic and tactical. Test plan mainly plans the scope, method and resource allocation of test activities from a macro perspective, while test specifications and test cases are specific tactics to complete test tasks.
What do you think is the key to good test case design?
The key to white-box test case design is to cover as many internal program logic results as possible with fewer use cases.
The key to black-box use case design is also to cover the module’s output and input interfaces with fewer use cases. It is impossible to test completely and find the most problems in a reasonable amount of time with the fewest use cases.
What are your testing career goals?
The more testing experience, the better the testing ability. So my career development was cumulative, working my way up to senior test engineer. In addition, I have a preliminary career plan, accumulated testing experience in the first three years, constantly updated and corrected myself, and did well in testing tasks.
What are the criteria for the end of the test?
From the micro point of view, it is defined in the test plan, for example, the System runs smoothly for 72 hours under a certain performance. In the current Bug Tracking System, there is no general serious Bug in this version, the number of common bugs is less than 3, and the Bug repair rate is more than 90% and other parameters, and then the development manager, test manager, The project manager co-signed to approve the Release.
On a macro level, testing is over when the software is completely gone.
What phases should a complete set of tests consist of?
Feasibility analysis, requirements analysis, outline design, detailed design, coding, unit test, integration test, system test, acceptance test
In your past work, what did a software defect (or Bug) record contain? How do I submit high quality software Bug records?
A Bug record should basically contain:
The bug number; Bug severity level and priority; Bug-generated modules; First, there should be a bug summary, describing the general content of the bug; Version of the bug; Bug Detailed description, including some screenshots and videos…. And so on; The test environment when the bug appears, the conditions are the corresponding operation steps;
High quality Bug logging:
Universal UI The UI for accurate defect reporting should be consistent with the UI of the tested software for easy search and location.
(Try to use jargon and expressions commonly used in the industry)
Use terminology and expression methods commonly used in the industry to ensure accurate and professional expression.
Each defect report contains only one defect
Each defect report contains only one defect, which enables the defect fixer to quickly locate a defect and focus on fixing only one defect at a time. The verifier verifies that only one defect at a time has been corrected correctly.
Non-reproducible defects are also reported
First, the defect report must demonstrate the ability to reproduce the defect. The defect that cannot be reproduced should be reproduced as much as possible. If the defect cannot be reproduced after all efforts are made, the defect should still be reported, but the frequency of the defect should be indicated in the report.
Clearly identify the defect type
According to the phenomenon of defects, summarize and judge the types of defects. For example, functional defects, interface defects, data defects, rationalization suggestions these are the most common types of defects or defects, and other forms of defects or defects also fall into one of these forms.
Clearly identify defect severity and priority levels
Always identify the difference between severity levels and priority levels. Serious problems may not be worth solving, and minor cosmetic problems may be treated as high priority. Description, concise, accurate, complete, reveal the essence of the defect, record the defect or the location of the defect the Description should accurately reflect the essence of the defect, short and clear. To facilitate the search for defined test defects in the software defect management database, it is a good practice to include the user interface (UI) at the time the defect occurred. For example, record the title of the dialog box, the name of the menu, and the name of the button. The use of automatic numerical serial number between short lines, the use of the same font, size, line spacing between the use of automatic numerical serial number between short lines, the use of the same font, size, line spacing, can ensure that each record format is consistent, standardized and professional.
Try to record only one operation per step
Keep it simple, organized and easy to repeat. Ensure that steps are complete, accurate, and brief to ensure quick and accurate repetition of defects. “Complete” means no missing, “accurate” means correct steps, and “brief” means no extra steps. According to the defect, you can choose whether to capture the image
In order to intuitively observe the defect or defect phenomenon, it is usually necessary to attach the interface where the defect or defect appears, and attach the picture as an attachment to the “attachment” part of the record.
In order to save space and truly reflect the nature of defects or defects, you can capture the full screen, active window and local area when defects or defects occur. In order to quickly locate and correct defects or defect locations, a Chinese reference map is usually required.
Attach necessary special documentation and personal advice and notes l
If a defect or defect arises from opening a particular document, the document must be attached so that the defect or defect can be reproduced quickly. In some cases, personal modification suggestions or notes may be attached to enable the defect or defect corrector to further clarify the appearance of the defect or defect.
Check for spelling and grammar defects
Before submitting each defect or defect, check spelling and grammar to make sure the content is correct and the defect is described correctly. The purpose of software defect management database is to facilitate defect location. Therefore, it is required to describe operation steps objectively, without modifying vocabulary and complex sentence patterns, so as to enhance readability. The above summarizes the specification requirements for reporting test defects. With the different testing requirements of software, testers will gradually develop good professional habits after long-term testing and accumulate corresponding testing experience, and constantly add new specification writing requirements.
In addition, you can constantly improve your skills by reading and learning test defect reports from other test engineers and comparing and thinking about your own previous test defect reports.
Defect Description content
The content of defect description can include defect operation steps, actual results, and expected results. The procedure makes it easy for the developer to reproduce the defect and fix it. Some developers are very bad at reproducing the defect, even though they understand the defect you are referring to.
But it simply cannot be reproduced, especially for new developers who are not familiar with the system. The actual result lets the developer know what went wrong, and the expected result lets the developer know what the correct result should be.
Black box testing and white box testing are two basic methods of software testing, please explain their advantages and disadvantages respectively!
The advantages of black box testing are: relatively simple, do not need to understand the internal code and implementation of the program; Has nothing to do with the internal implementation of the software; From the user’s point of view, it is easy to know what functions users will use and what problems they will encounter.
Based on the software development documentation, it is also possible to know what functions the software implements in the documentation; It is convenient to do automatic testing of software.
The disadvantages of black box testing are as follows: it is impossible to cover all code, and the coverage is low, which can only reach 30% of the total code volume; Automated tests have low reusability.
The advantages of white box testing include: it helps software testers increase code coverage, improve code quality, and discover hidden problems in code.
The disadvantages of white-box testing are that the program runs on many different paths and it is not possible to test all of them. Based on code, testing can only test whether developers do the right thing, but not know whether the design is correct or not, may miss some functional requirements; When the system is large, the cost of testing can be very high.
How to test a paper cup?
Function: with a cup of water to see the leakage does not leak; Can the water be drunk
Safety: There is no poison or bacteria in the cup
Reliability: Degree of damage caused by a cup falling from different heights
Portability: whether the cup can be used normally in different places, temperatures and other environments
Compatibility: Whether the glass can hold juice, water, alcohol, gasoline, etc
Ease of use: whether the cup is hot, whether there are anti-slip measures, whether it is easy to drink
User documentation: The user manual describes the usage, restrictions, and conditions of use of the cup in detail
Fatigue test: Put the cup in water (Case 1) for 24 hours to check the time and situation of leakage; Fill the gasoline (case 2) and leave it for 24 hours to check the time and situation of leakage, etc
Pressure test: use a needle and keep adding weight to the needle to see how much pressure will penetrate
What is the purpose of the test planning exercise? What should the contents of the test plan document include? Which are the most important?
A software test plan is a programmatic document that guides the testing process:
The leader can carry out macro-control according to the test plan and allocate corresponding resources. The tester can understand the test situation of the whole project and the work to be carried out at different stages of the project test, so that other personnel can understand the work content of the tester. Related cooperation includes product overview, test strategy, test method, test area, test configuration, test cycle, test resources, test communication, risk analysis and so on. With the software testing plan, the project members participating in the testing,
In particular, test managers can clarify test tasks and test methods, maintain smooth communication in the test implementation process, track and control the test progress, and deal with various changes in the test process.
6 elements of test plan compilation (5W1H) :
Why — why these tests are carried out; What – what to test, what to do at different stages of work; When – Test the start and end times of different stages; Where – documentation, location of defects, test environment, etc. Who — The composition of relevant personnel of the project, and which testers are arranged to carry out the tests; How – how to do, use what test tools and test methods for testing the test plan and test specifications, test cases, is the strategic and tactical relationship between test plan mainly from the macro planning the scope of testing activities, methods, and the allocation of resources, and test specifications, test cases is to complete test task specific tactics.
So the most important thing is to test the test strategy and test methodology (preferably reviewed first).
What are the common methods of designing test cases for black box testing? Please give specific examples to illustrate the application of these methods in the test case design work.
1) Equivalence class division: Equivalence class refers to a subset of an input field. In this subset, each input data is equivalent to exposing errors in the program. It is reasonably assumed that testing a representative value of an equivalence class is equivalent to testing other values of that class.
Therefore, all input data can be reasonably divided into several equivalence classes, and a small amount of representative test data can be used if one data from each equivalence class is taken as the input condition of the test. Get good test results. Equivalence classes can be divided into two different cases: valid equivalence classes and invalid equivalence classes.
2) Boundary value analysis method: it is a supplement to equivalence class division method. My experience in testing has taught me that a large number of errors occur at the boundary of the input or output range, not inside the input or output range. Therefore, designing test cases for various boundary cases can detect more errors.
When designing test cases using boundary value analysis, the boundary cases should be determined first. In general, the boundary of input and output equivalence classes is the boundary case that should be tested. You should select values that are exactly equal to, just above or just below the boundary as test data, rather than typical or arbitrary values in the equivalence class.
3) Error guessing method: the method of speculating all possible errors in the program based on experience and intuition, so as to design test cases in a targeted way.
The basic idea of the error prediction method is to list all possible errors in the program and special cases prone to errors, and select test cases according to them. For example, many common errors in modules were listed during unit testing. Errors found in previous product tests, etc., are the summary of experience.
There are also cases where the input data and the output data are zero. Input form is blank or input form has only one line. These are all error-prone situations. You can select examples in these cases as test cases.
4) Causality diagram method: the equivalence class division method and boundary value analysis method introduced above both focus on the input conditions, but do not consider the connection between the input conditions and their combination. Some new situations may arise when you consider combinations of input conditions.
But it is not easy to examine the combination of input conditions, and even if all input conditions are divided into equivalence classes, there are quite a few combinations between them. Therefore, consideration must be given to a method suitable for describing a combination of conditions,
Consider designing test cases in a form that generates multiple actions accordingly. This requires the use of causal diagrams (logical models). The final result of the causal diagram method is the decision table. It is suitable for checking various combinations of program input conditions.
5) Orthogonal table analysis method: the combination of a large number of parameters may lead to a surge in the number of test cases. At the same time, there is no obvious difference in priority between these test cases, and testers are unable to complete so many tests.
Some use cases can be reduced through orthogonal tables to achieve the possibility of having as few use cases as possible to cover as large a range as possible.
6) Scenario analysis method: it refers to simulating the operation steps of users according to user scenarios. This is similar to the causal diagram, but the execution depth and feasibility may be better.
7) State diagram method: obtain all states of the system under test through input conditions and system requirements, and obtain output conditions through input conditions and states; The test case of the system under test is obtained by input condition, output condition and state.
8) The outline method: The outline method is a requirement-focused approach that converts requirements into an outline in order to list various test conditions. The outline is represented as a tree structure with a unique path between the root and each leaf node.
Each path in the outline defines a specific set of input criteria for defining test cases. The number of leaves in the tree or paths in the outline gives an approximate number of test cases needed to test all the functionality.
Describe in detail the complete process of a test activity. (For your information, this answer is mainly the practice of waterfall model)
The project manager completes the requirement document through communication with the customer, and the developer and tester jointly complete the review of the requirement document. The review content includes: where the requirement description is unclear and where there may be obvious conflicts or functions that cannot be realized.
The project manager completes the project plan by integrating input from developers, testers, and customers. SQA then enters the project and starts doing statistics and tracking
The requirements analysis document is completed by the developer from the requirements document and reviewed by the tester. The main content of the review includes whether there are omissions or differences in understanding between the two parties. The tester completes the test plan document, which includes the content described above.
The tester starts writing test cases from the revised requirements analysis document, while the developer completes the outline design document and the detailed design document. These two documents serve as supplementary material for testers writing test cases.
After the test cases are completed, testing and development need to be reviewed.
Testers build the environment
The developer submits the first release, and there may be unfinished features that need to be explained. Testers run tests, find bugs and submit them to BugZilla.
The development submitted the second version, including Bug fixes and added some features, and the testers tested it.
Repeat the above work, generally 3-4 versions after the number of bugs reduced to meet the requirements of shipment.
If there are customer feedback problems, need the help of the tester to reproduce and retest.
Bug. admin tool trace process (using BugZilla as an example)
The tester finds a BUG, submits it to Bugzilla with the status new, and the recipient of the BUG is the developer interface person
The development interface assigns the BUG to the developer of the relevant module, and the status is changed to assigned. The developer and the test confirm the BUG. If the BUG is my own, it is set to receive. If it’s another developer’s problem, forward it,
It’s up to the next developer to do this; If it’s not a problem, it needs to be discussed and confirmed, rejected, and then the tester closes the problem.
If the developer accepts the BUG and fixes it, change the BUG status to fixed and tell the test in which version it can be tested.
The tester tests in the new version and rejects validation if the problem persists. If it has been fixed, close the BUG.
In your opinion, how to improve the efficiency and effect of communication between testers and developers? What is the key to maintaining good relationships between testers and the rest of the development team?
Communicate face to face as much as possible. Secondly, communicate directly on the phone. If only through Email and other non-timely communication tools, emphasize a deep understanding of the features and be able to express clearly.
It is also effective to use test management tools such as TestDirector, and note that the bugs are accurately described in TestDirector.
# Build good communication between testers and developers on the team:
One is sincerity, two is team spirit, three is the common language in the professional, four is to matter not people, work first
You can also increase goodwill by pointing out minor problems rather than entering a BUG Tracking System.
What interests you most about testing? Why is that?
Answer this interview question, there is no fixed unified answer, but may be many enterprises will ask. Provide the following answers for examination:
The biggest interest, feeling this is a challenging job;
Testing is an experience industry, the longer I work, the more I can feel the difficulty and fun of doing a good test
Through their own work, can make software products more and more perfect, from the experience of fun
Pay attention to the following aspects when answering such questions:
Try to match your interest with the company’s technical path. For example, if the company is a database application company, then show your interest in database testing and hope to improve your database skills through testing.
Indicate that the purpose of doing the test is to improve your ability, but also to better do the test; Promotion capacity is not for later development or other, unless the employer has such arrangements.
Don’t express too much interest outside the scope of the company. For example, the company does financial software, but you show an interest in game software. Or the job is to do JAVA development, and your interest is in C programming.
What do you think are the advantages of testing?
There is no fixed answer to this interview, but you can refer to the following points and combine their own characteristics:
I am resilient, patient, organized, like to face challenges, confident to do everything well, strong communication skills, and have received good comments from previous managers
Briefly describe what you have done in your previous jobs and what you are familiar with. The reference answers are below.
My main work in the past was system testing and automated testing. In the system test, it mainly tests the business logic function of BOSS system and the Class 5 characteristics of softswitch system. Performance testing, mainly stress testing,
Obtain the system response time and system resource consumption for each different number of requests. Automated testing is mainly through the combination of writing scripts and some third-party tools to test the characteristics of soft switch testing.
In testing, I felt it was important to have a completely accurate understanding of the user’s needs. In addition, the management of bugs should be based on requirements. Not all bugs need to be modified.
Testing requires patience and care, because in the new version, while most of the bugs that were originally found are fixed, the functionality that was once correct may become incorrect. So focus on iterative testing and regression testing.
What is static in C/C++.? In the body of a function, a variable declared static remains static for the duration of the call.
Inside a module (but outside of a function), a variable declared static can be accessed by functions used inside the module, but not by other functions outside the module. It is a local global variable. A function declared static in a module can only be called by other functions in the module. That is, this function is restricted to the local scope of the module in which it is declared
25 database quizzes you must ask in an interview
1) What is database testing?
Database testing is also called back-end testing. Database tests fall into four distinct categories.
[if! SupportLists]· [endif] Data integrity test
[if! SupportLists]· [endif] Tests data validity
[if! SupportLists]· [endif] Database related performance
[if! SupportLists]· [endif] Tests functions, programs and triggers
2) What do we normally check for in database tests?
Typically, what we check in DB Testing is:
[if! SupportLists]· [endif] Constraint check
[if! SupportLists]· [endif] Verify the field size
[if! SupportLists]· [endif] Stored procedures
[if! SupportLists]· [endif] Matches the application field size to the database
[if! SupportLists]· [endif] Index of performance-based questions
3) Explain what data-driven testing is?
In a data table, to test multiple data, use data-driven tests. By using it, it is easy to replace arguments from different places at the same time.
4) What are connections and refer to the different types of connections?
Join is used to display two or more tables of the Join type:
[if! SupportLists]· [endif] Naturally join
[if! SupportLists]· [endif] Internal connection
[if! SupportLists]· [endif
[if! SupportLists]· [endif] Cross join
The external connection is divided into two parts:
[if! SupportLists]· [endif] Left external connection
[if! SupportLists]· [endif] Right external connection
5) What are indexes and refer to the different types of indexes?
Indexes are database objects that are created on columns. Access them frequently for quick access to data. The different types of indexes are:
[if! SupportLists]· [endif]B tree index
[if! SupportLists]· [endif] Bitmap index
[if! SupportLists]· [endif] Aggregate indexes
[if! SupportLists]· [endif] Coverage index
[if! SupportLists]· [endif] Non-unique index
[if! SupportLists]· [endif] Unique index
6) What steps did the tester take when testing the stored procedure?
The tester will check the standard format of the stored procedure and check if the fields are correct, such as update, join, index, delete mentioned in the stored procedure.
7) How do you know if a database test has triggered a trigger?
When you query the public audit log, you know if a trigger is triggered. It is located in the audit log, where you can see the triggers that fired.
8) What are the steps to test data loading in database testing?
The following steps need to be followed for test data loading
[if! SupportLists]· [endif] should know the source data
[if! SupportLists]· [endif] The target data should be known
[if! SupportLists]· [endif] Check source and target compatibility
[if! SupportLists]· [endif] In SQLEnterprise Manager, open the corresponding DTS package and run the DTS package
[if! SupportLists]· [endif] You must compare the target and data source columns
[if! SupportLists]· [endif] Check the number of target and source lines
[if! SupportLists]· [endif] After updating the data in the source, check that the changes are displayed in the target.
[if! SupportLists]· [endif] Checks for NULL and garbage characters
9) How do I test SQL queries in QTP without database checkpoints?
By writing scripts in VBScript, we can connect to the database and test queries and databases.
10) Explain how to use SQL queries in QTP.
In QTP that uses output database checkpoints and database checks, you must select the SQL manual query option. After selecting the manual query option, enter Select query to get the data in the database, and then compare expectations with reality.
11) What is the method of writing test cases for database tests?
Writing test cases is like functional testing. First, you must understand the functional requirements of your application. Then you must decide on the parameters to write the test case
[if! SupportLists]· [endif] Targets: List the targets you want to test
[if! SupportLists]· [endif] Input method: Write the operation method or input to be executed
[if! SupportLists]· [endif] Expectations: How should it appear in the database
12) What SQL statements did you use in database tests to manage and manipulate test tables?
Statements such as SELECT, INSERT, UPDATE, and DELETE are used to manipulate tables, while ALTER TABLE, CREATE TABLE, and DELETE TABLE are used to manage tables.
13) How do I test database programs and triggers?
To test database procedures and triggers, you must know the input and output parameters. The EXEC statement can be used to run the procedure and check the behavior of the table.
[if! SupportLists]· [endif] Open the database project in Solution Explorer
[if! SupportLists]· [endif] Now, on the View menu, click database Schema
[if! SupportLists]· [endif] Opens the project folder from the Architecture View menu
[if! SupportLists]· [endif] Right-click the object you want to test and click the Create Unit Tests dialog box
[if! SupportLists]· [endif] Create a new language test project
[if! SupportLists]· [endif] Select a) Insert unit tests or b) Create new tests, and then click OK
[if! SupportLists]· [endif] The items that must be configured are completed by clicking the Project Configuration dialog box.
[if! SupportLists]· [endif] Click OK after the configuration is complete.
14) How are test cases written according to requirements, and do these requirements represent the exact functionality of the AUT (the application under test)?
To write test cases based on requirements, you need to thoroughly analyze requirements in terms of functionality. After that, you can consider writing test cases using appropriate test case design techniques, such as equivalent partitioning, black box design, cause-effect drawing, and so on. Yes, these requirements represent the exact function of the AUT.
15) What is a DBMS?
DBMS stands for database management system, and there are different types of DBMS
[if! SupportLists]· [Endif] Network model
[if! SupportLists]· [endif] Hierarchical model
[if! SupportLists]· [endif] Relational model
16) What is DML?
DML stands for Data Manipulation Language, which is used to manage data using schema objects. It is a subset of SQL.
17) What is a DCL command? What are the two commands used by the DCL?
DCL stands for Data Control Language, which is used to control data.
The two types of DCL commands are:
Authorization: By using this command, the user can access the database permission
Undo: With this command, the user cannot access the database
18) What is white box testing and black box testing?
Black box testing means testing the output of the software when given a particular input. This test is usually performed to see if the software meets the user’s requirements. No specific functional output is required to run this test.
Perform white-box tests to check the accuracy of the program’s code and logic. This test is done by programmers who understand the logical flow of the system.
19) How does QTP evaluate test results?
When the test is complete, THE QTP will generate a report. This report displays checkpoints, system messages, and errors detected during testing. The test results window displays any mismatches encountered at the checkpoint.
20) Explain the QTP test process?
[if! SupportLists]· [ENdif]QTP test process is based on the following steps:
[if! SupportLists]· [endif] Create GUI (Graphical user interface) mapping file: Identifies GUI objects that must be tested
[if! SupportLists]· [endif] Create a Test script: Record the test script
[if! SupportLists]· [endif] Debug Tests: Tests should be debugged
[if! SupportLists]· [endif] Run tests: Test cases should be run.
[if! SupportLists]· [endif] View the result: The result reflects the success or failure of the test
[if! SupportLists]· [endif] Report detection: If the test fails, the cause will be recorded in the report detection file
21) What is load testing and give some examples?
To measure system response, perform a load test. If the load exceeds user mode, it is called a stress test. An example of a load test is to download a set of large files, execute multiple applications on a single computer, and have the server receive a lot of E-mail and assign many tasks to the printer.
22) How do I test the database manually?
Testing the database manually involves checking the data on the back end and seeing if the addition of front-end data affects the back end, deletes, updates, inserts, and so on.
23) What does RDBMS stand for, and what are important RDMBS that SQL uses?
RDBMS stands for relational database management system using SQL. The important RDBMS used by SQL are Sybase, Oracle, Access, Ingres, Microsoft SQL Server and so on.
24) What is performance testing and what are its bottlenecks?
Performance testing determines the speed of computer system performance. It includes quantitative tests such as response time measurements. The problem with performance testing is that you always need highly trained and experienced people, and the tools you use are expensive.
25) What are DDLS and what are their commands?
To define the database structure, Developer uses DDL. DDL stands for Data definition Language. DDL commands include Create, Truncate, Drop, Alter, Comment, and Rename.
Conclusion:
Finally, I recommend a learning material to share with you: 718897738 group of automatic test bull has sorted out a lot of learning materials for us, automation, interface, performance and so on learning materials!
Life is a process of rowing upstream, not to advance is to retreat, let’s refuel together!