软件测试实习总结

实习总结

20xx年x月x日。我怀着对提高并实现自我价值的心态,走进深圳走秀网络科技有限公司的大门,开始了自己大学里兼职实习工作。转眼间。6个月的实习时间就要过去了。回想起这段时间的工作过程,我深深的认识到在走秀网实习的选择是绝对正确的,走秀网和公司的同事们对我个人产生的积极影响也是超越我料想之中的。现将这段时间的工作进行如下总结。

首先,要具有良好的学习能力。刚进走秀,带我的老大是哈尔滨人,我跟她很投缘。开始的一个星期,我只是熟悉公司的一些业务和我们前端的测试范围,在熟悉业务的过程中,我发现这些页面上的东西看上去挺简单的,但是要深入了解还是需要很长的一段时间。期间老大叫一个老员工带着我去测试一些之前xiu2.0所遗留的简单的bug。走秀网的测试部还比较大,所以对工作的流程和上线之前的版本控制的非常严格。我们在上线之前,会经过两套环境,功能测试环境和镜像环境,功能测试环境是对需求和功能的一个详细的验证环境,镜像环境是模拟生产环境回归之前我们在功能测试环境上锁遗留的一些小的bug。因为不知道这些转测试的bug是怎么产生的,所以需要去跟开发人员沟通,开始的时候自己一个人不敢过去开发部,就让老员工(才哥)带着过去,一段时间过后,我开始自己去和开发沟通交流,从发现问题的重现,到催促开发修改和转测试,这一段时间让我深刻体会到沟通时多么重要。

在走秀期间,我们测试部总监还会对我们不定时的培训。教会我们测试的工作流程和每个阶段应该展开的工作范畴。作为测试,必要会使用的缺陷管理工具bugzilla和测试用例管理工具testlink,还给我们培训了,如何使用自动化工具ruby+watir来对一些测试点进行自动化脚本的编写。慢慢的,在对公司的业务了解的比较透的时候,老大就开始让我们自己对一些小需求进行测试,测试的过程中,不仅仅是对页面和表面功能进行测试,还要根据需求文档和页面的显示对数据库表进行查询操作,查看页面的显示和功能是否和数据表里面的一致,还要在后台日志中查看是否有报错。所以,测试并不是像我想象中的那么简单,不是在页面上点来点去就可以测的好的。

实习可以使每一个学生有更多的机会尝试不同的工作,扮演不同 的社会角色,逐步完成职业化角色的转化,发现自己真实的潜力和兴趣,以奠定良 好的事业基础,也为自我成长丰富了阅历,促进整个社会人才资源的优化配置。 作为一名学生,我想学习的目的不在于通过毕业考试,而是为了获取知识,获 取工作技能,换句话说,在学校学习是为了能够适应社会的需要,通过学习保证能 够完成将来的工作,为社会做出贡献。然而步出象牙塔步入社会是有很大落差的, 能够以进入公司实习作为缓冲,对我而言是一件幸事,通过实习工作了解到工作的 实际需要,使得学习的目的性更明确,得到的效果也相应的更好。

人要想成功及获得好的业绩,必须牢记一个规则:我们永远不能将个人利益 凌驾于团队利益之上,在团队工作中,会出现在自己的协助下同时也从中受益的情 况,反过来看,自己本身受益其中,这是保证自己成功的最重要的因素之一。

20xx年x月x日实习生:管玮玮

 

第二篇:软件测试复习总结

1.What is testing? ? ? ? ?

Finding defects in a controlled manner

Detecting the level of quality of the test object Demonstrating the gap between specifications and the actual product

Demonstrating that the end product functions as called for in the requirements 2.what is software testing?

Software testing: is the process of executing software in a controlled manner , in order to answer the question “ Does the software behave as specified?”

Software testing is often used in association with the terms verification and validation. 3.Why do we test? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

Provide confidence in the system Validate software quality Identify areas of weakness Establish the degree of quality Reduce time-to-market

Verify integration of business processes Application Software Hardware System Software Procedures Documentation Functionality Performance Usability

Interoperability (between different applications and systems)

5.Define the following items software:

1).Bug:After coding and compiling we'll find the mismatch between expected and actual result.

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.

2).Debugging :is an activity which supports testing but cannot replace testing.

3).Defect:The software defect is present in the software, among the undesirable or unacceptable deviation 4).Error:it's a mistake in programmer.

E.g. when we compile a programmer in C language there we can see the number of errors and warning.

Software error refers to the software cycle do not want to appear or unacceptable human error

production

1

production

6.What are the Levels of testing ? ? ? ?

Unit Testing

Software integration testing System testing Acceptance testing

They know coding knowledge They don?t no coding knowledge 7.Compare verification and validation

Verification: Verification is the checking or testing of items, including software for conformance and consistency with an associated specification 1). It is a Quality improvement process.

2)It is involve with the reviewing and evaluating the process. 3). It is conducted by QA team. 4). Verification is Correctness.

5). Are we producing the product right?

Validation: Validation is the process of checking that what has beenspecified is what the user actually wanted. 1). it is ensures the functionality.

2). It is conducted by development team with the help from QC team.

3). Validation is Truth.

4). Validation is the following process of verification. 5). Are we producing the right product?

8.draw the software testing life cycle diagram.(p36) 9.Test plan

A test plan states what the items to be tested are , at what level they will be tested, what sequence they are to be tested in , how the test strategy will be applied to the testing of each item and describe the test environment. ?

Some of the test plan documents are Acceptance test plan, System test plan Integration test plan Unit test plan

10.write a few points about test plan? ? ? ? ? ? ?

The testing process of software should also require good plan.

Test plan document is the most important document that brings in a process – oriented approach. The test plan is a mandatory document. You can?t test without one.

For simple, straight-forward projects the plan doesn?t have to be elaborate but it must address certain items. As identified by the “American National Standards Institute and Institute for Electrical and Electronic Engineers Standard 829/1983 for Software Test

4.What do we test?

Documentation”, the following components should be covered in a software test plan. 11.write sample test case method.

12.Write the importance of software testing. ? ? ?

The economies of ALL developed nations are dependent on software

More and more systems are software controlled More and more businesses depend on software for their success

13.Why do software testing?

“To find the bugs!” is the instinctive response and many people, developers and programmers included, think that that?s what debugging during development and code reviews is for, so formal testing is redundant at best. But a “bug” is really a problem in the code; software testing is focused on finding defects in the final product. 14.Define the following items:

1).Black box testing:Black-box tests in the test, the procedure can not be opened as a black box, in the process without considering the internal structure and internal features of the case, the test in the test program interface Branch

2).White box testing: is also called Structural or Glass box testing.involves looking at the structure of the code. When you know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification.

3).Unit testing: in which each unit( basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented

4).Component testing: .is a software verification and validation method in which a programmer tests if individual units of source code are fit for use.

5).Integration testing: is the phase in software testing in which individual software modules are combined and tested as a group.

(in which progressively larger groups of tested components corresponding to elements of the architectural design are integrated and tested until the software works as whole.) 6).Functional testing: refers to tests that verify a specific action or function of the code.

7).System testing : System test is confirmed software, computer hardware, peripherals, networks, combined with other elements to carry out a variety of assembly and testing of information systems and validation testing, the purpose of the demand through the comparison with the system and found that the development of System and user requirements where inconsistent or contradictory, which raised more comprehensive program.

2

(in which the software is integrated to the overall product and tested to show that all requirements are met.) 8).End-to-end testing:

9).Acceptance testing:often the final step before rolling out the application.Usually the end users who will be using the applications test the application before ?accepting? the application.

(testing the software with customers data at customers site.)

10).Regression testing:testing needs to be done to ensure that it works as specified and that it has not negatively impacted any functionality that it offered previously. 11).Load testing:is primarily concerned with testing that can continue to operate under a specific load, whether that be large quantities of data or a large number of users. 12).Stress testing: System test is confirmed software, computer hardware, peripherals, networks, combined with other elements to carry out a variety of assembly and testing of information systems and validation testing, the purpose of the demand through the comparison with the system and found that the development of System and user requirements where inconsistent or contradictory, which raised more comprehensive program.

13).Performance testing:is executed to determine how fast a system or sub-system performs under a particular workload.

14).Usability testing:is needed to check if the user interface is easy to use and understand.

15).Security testing:is essential for software that processes

confidential

data

to

prevent system

intrusion by hackers.

15.Types of Integration Testing

the lowest level components are tested first, then used to make easier the testing of higher level components.

the top integrated modules are tested and the branch of the module is tested step by step until the end of the related module.

with bottom up testing. 16.Integration Testing Steps:

Integration Testing typically involves the following Steps: Step 1: Create a Test Plan

Step 2: Create Test Cases and Test Data

Step 3: If applicable create scripts to run test cases Step 4: Once the components have been integrated execute the test cases

Step 5: Fix the bugs if any and re test the code

Step 6: Repeat the test cycle until the components have been successfully integrated

17.What is Software Quality Assurance?

Software QA involves the entire software development PROCESS - monitoring and improving the process, making sure that any agreed-upon standards and procedures are followed, and ensuring that problems are found and dealt with.

It is oriented to 'prevention'. 18.Why does Software have bugs? ? ? ? ? ? ? ?

Miscommunication or no communication Software complexity Programming errors changing requirements time pressures

poorly documented code software development tools

executing the code.

Dynamic analysis looks at the behavior of software while it is executing.

24.How to write a System Test Case?

A Test Case describes exactly how the test should be carried out. ? ? ? ? ? ?

The System test cases help us verify and validate the system.

The System Test Cases are written such that: hey cover all the use cases and scenarios

The Test cases validate the technical Requirements and Specifications

The Test cases verify if the application/System meet the Business & Functional Requirements specified The Test cases may also verify if the System meets the performance standards 25.Test Case ? ? ?

The format of the System Test Cases may be like all other Test cases as illustrated below: Test Case ID

Test Case Description:

? ?

? ? ?

Input Data Expected Result Actual Result

What to Test? How to Test?

19.What is software 'quality'?

Quality software is reasonably bug-free, delivered on time and within budget, meets requirements and/or expectations, and is maintainable. 20.What is 'good code'?

'Good code' is code that works, is bug free, and is readable and maintainable.

Some organizations have coding 'standards' that all developers are supposed to adhere to, but everyone has different ideas about what's best, or what is too many or too few rules.

21.What is 'good design'?

Design' could refer to many things, but often refers to 'functional design' or 'internal design'.

Good internal design is indicated by software code whose overall structure is clear, understandable, easily modifiable, and maintainable; is robust with sufficient error-handling and status logging capability; and works correctly when implemented.

Good functional design is indicated by an application whose functionality can be traced back to customer and end-user requirements.

22.What is the 'software life cycle'?

The life cycle begins when an application is first conceived and ends when it is no longer in use.

It includes aspects such as initial concept, requirements analysis, functional design, internal design, documentation planning, test planning, coding, document preparation, integration, testing, maintenance, updates, retesting, phase-out, and other aspects.

23.Static analysis investigates the source code of software, looking for problems and gathering metrics without actually

3

相关推荐