1, developed commit low-level error how to do?
First of all to develop good coding specification, when a low-level functions do not wrong, point out errors heart. Let themselves be tested, reflection isolate the error.
2, you conducted those tests, what good?
I mainly engaged in web testing, built environment, program integration testing, system testing, regression testing. As well as the preparation of test cases, user manual, functional testing documentation.
3, how do developers say it is not bug?
He will tell develop their own opinion, not opinion and put the project managers decided to submit bug.
4, your career plans? *
Consolidate and test knowledge and improve understanding of capacity needs.
Learn automated testing, and use. After the end of the learning technology to lead the test team.
Strive to reach the final Test Manager level.
5. What test is qualified? *
Be able to cover all the test points
6, defect reporting test composition?
Defect number, title defect, the defect level described finite defect,
the defect level of priority, the module belongs to a defect, a defect version belongs, belongs to the developer defect,
the input data, and outputs the result, a defect analysis.
C / S mode, confirmed using an alternating method is client or server side issues
7, test cases including those
with Example No., a test environment, with the title embodiment, the input data, expected results
8, the software and the purpose of the review staff
personnel: customers, project managers, developers, testers
aim: to see if the software is still a problem. Whether running on different platforms, and customers to understand whether there are inconsistencies, whether there are areas for improvement
* 9, what software testing? purpose? *
By manual or automated operation, run software programs to see if they meet customer needs.
Objective: The shortest time to find out as much of the software is indeed defective
10, compatibility test
to check software on different software and hardware platform is functioning correctly.
The main view different operating systems, browsers, databases, whether running in different versions
11. Why is software testing?
Not tested software can not guarantee the same quality, like iso quality certification.
Tests find problems that are submitted to the development of improved software quality results when the software is released.
12, there are those types of software testing? Differences and relations?
Common: Functional testing, performance testing, interface testing.
Functional test: the largest proportion, also called black-box (without looking at the code). When dynamic testing requires test software function, the software does not need to test the internal structure and processes.
Technical methods are: equivalence partitioning method, boundary value analysis, error guessing, cause and effect diagrams and comprehensive strategy.
Performance Testing: simulate a variety of normal, abnormal peak condition through automated testing tools, the performance test system.
Load testing, stress testing belong to this. Load Test: determine system performance in the work load, the load primary key objective is to increase the system performance indicators change; stress test: through the bottleneck of the system, the system can obtain the maximum level of service provided.
Interface test: the user interface of the software is good or bad decision the first impression. Reasonable interface brings a relaxed feeling, failed interface frustrating, so powerful in vain.
Difference: Functional testing is focused software functions each of possible problems. Multi-user concurrent performance testing software stability and robustness. Interface testing is focused user experience and ease of use.
13, the key to a good test case?
White box: The method covers less as much of the internal logic of the program results.
Black box testing: fewer overlay module output and input interfaces use cases. A minimum with the most problems were found within a reasonable time.
Must be considered viable and feasible, and (4) actual output (1) Input (2) The detailed operation of step (3) of the expected output
14, differences and relations black box, white box, unit, integration, system, acceptance testing?
Black Box: Known functional design specifications, test the main entrance of each function is complex requirements.
White box: Known internal working process, testing the internal operation of the main entrance of each composite design specifications.
Black box test means that the software interface is performed, the test subject considered as a black box, and do not consider the internal logical structure characteristic internal procedures, see the specification only check whether the composite demand requirements. Black box - "functional test (or data driven test)
15, the software development process and the division of roles?
Testing with development needs analysis and discussion, designated "Project test plan," according to the requirements specification, writing test cases, test environment.
Testing is responsible for new product testing, the original product upgrade testing, problem-solving process responsible for tracking software, software development documents, development of standardization and management development departments of product documentation, making user manuals, operating manuals, product limit testing, surveillance software development implementation process and improve software quality.
16, the software development process and the division of roles?
Development and testing of a meeting to discuss needs. The analyst needs analysis written instructions, discuss the feasibility of the three departments. The detailed description given design, development coding system flow chart is given. According to this test, given bug statistics.
17 different types of test connections and differences?
Functionality, performance, reliability, security, load,
pressure, installation \ Uninstall, Start \ Stop, compatible, interconnection testing,
documentation, regression, usability, capacity testing
18, including test plan work?
When the work content of effective organization and planning to ensure that the test work effectively carried out. Including test objectives, test scope definition, test method selection, testing milestones, testing, resource management and configuration.
The most important goal of the test, because he is ultimately the result of software testing
19, performance testing tools, the yard, the practical application
LoadRunner. To record the test procedure, an analog of a plurality of users play out.
(1) visural user genertor: create a script, select the protocol, recording operations, editing operations
(2) central controller controller: scheduling virtual users. Create a scene, select the script, create a virtual user, design shedual, Spoofer set ip
(3) run the script, analyze shedual
(4) analysis of test results
20, compatibility
platform compatibility, network compatibility, database compatibility, compatible data format.
Category defect levels
high: test drivers, system crashes, data losses, not functioning
very high: leads to unstable software features, functions to achieve error, process error
Intermediate: a parity error, a rare failure, typos, does not affect the function, experience the impact of
low-level: small problems do not affect
21, the defect life cycle of
new bug- submit bug- confirm bug- with non-bug- repair bug- verify bug- closed bug
22, the end of the test criteria
1) twelve the number of defects to achieve the project objectives and requirements of quality management, testing, development returns to suspend
2) significant estimates and project schedule deviations, need to suspend or terminate
3) the new demands of big change, the need to modify test plans and test then with Example
4) suspended development, testing also suspended, data backup suspend
5) all functions for the performance test of 100%
23, the testing life cycle
requirements specified test plans and review - written test - test case execution -bug Management - Test Report Output
24, self-introduction routine
1) are pleased to get an interview ...... I want to prove that Ho candidate ...... want to get your approval ......
2) ask the interviewer: You see I continue to introduce your project or question concerns?
25, Projects
1) first overall and then local, the project five dimensions: the size (code size, the scale of demand, the use case size, effort, schedule, quality, cost), test procedures, roles and responsibilities, project, their role, their own features (well done, difficulties encountered, do poor), and finally the feelings and experiences.
26, Database issue
database CRUD (insert, delete, update, select );
table structure CRUD (create, drop, alter, describe );
stored procedure;
triggers,
27, Linux systems
common 50 commands (find, -name, type, perm , user, group, ctime, atime)
familiar with vi, familiar linux set up a test environment. LAMP environment to build.
28, defect-related
defect tracking process (process basic elements), meaning the overall process (will paint), single defect of 20 properties, attributes, describe how good the defect list, the defect of single-5C principle, steps to reproduce defects. Do you think the most classic bug
29, with related cases
use Form factor cases, case design engineering methodology, approach requires
how to use.
How to use case review, the assessment from those dimensions, easy to use design needs of those cases only structure
30, the software testing process
familiar with the product / project - needs assessment - testing requirements - Test Plan - Test Plan - test - pre-test, the first round of formal testing - the second round of regression testing - the third round of testing, test report - Summary - testing Guide
31 network-related
basic networking knowledge (emphasis TCP / IP protocol)
32, testing tools
Performance testing tools:
automated testing tools:
Test management tools:
How to test a given software
tips: from the quality of the model, testing tools, test methods, test procedures, exploratory testing, macro resolved, then explain onlookers case design
33, excellent quality engineers
to communicate, five heart engineers, the pursuit of perfection
34, what you want to ask it?
Satisfaction: The first expressed his thanks and asked if the next round of interviews, when, and what to do to prepare;
like a general situation: thank, for their performance is not satisfactory, give me some advice;
bad: thank, recognize inadequate hope Advice
35, write test cases structural
functionality, interface UI, ease of use, security, compatibility
36, STAR law
S (situation): Project belong to what type of cycle long
T (task): Team division of labor, your character
A (action): specific implementation, what he was doing
R (result): final outcome, your reward
37, how to test cups
functionality: leaks; whether to drink water
safety: there is no bacteria
Reliability: the extent of the damage to fall
Portability: different places, the use of temperature and humidity
Compatibility: receiving juice, beer, soda, gasoline such as
ease of use: is hot, non-slip, easy drinking
user documentation: The instruction manual for use, restrictions, conditions of use described
fatigue test: were installed in Sheung Shui, gasoline for 24 hours, leak case
stress test: The town continues to pressure, Up to withstand pressure