Cool Interview Tips

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.

Well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application's objects. If the application was well-designed this can simplify test design.

Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. This can be done with checklists, issues lists, walkthroughs, and inspection meetings. Validation typically involves actual testing and takes place after verifications are completed.

Poor Communication – This is due to miscommunication for a developer as he don’t know what is needed by a customer. Or customers have unrealistic expectations. Poorly written requirements-This occurs when requirements are unclear, incomplete, not testable and too general. Schedules which are unrealistic-This occurs when too much of work is crammed in too little time. Inadequate testing –if none knows whether or not software is good until customers complain or system crashes. Adding new features after development is underway –This is a common practice to add new features after development is underway.

Good test engineer is one swho · Has a strong desire for quality, and "test to break" attitude. · who takes the point of view of the customer, · Has a strong desire for quality, Tactful and diplomatic · Has good oral and written communication skill. ·Has previous worked in software development .

In quality assurance Documentation plays a critical role, ALL the designs,Specifications ,code changes, test plans, business rules, inspection reports, configurations, test cases, bug reports, user manuals should be documented, all the practices should be documented, so that they are repeatable. Use documentation change management if possible, ideally there should be a system for easily finding and obtaining of documents and determining what document will have a particular piece of information.

A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The completed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product.

A test case is a document that contains particulars such as Test case Name, objective, test case identifier, test conditions/setup, Input data requirements/steps and expected results.A test case describes an input, action, or event and its expected result, in order to determine if a feature of an application is working correctly, since it requires you to completely think through the operations of the application the process of developing test cases can help find problems in the requirements or design of an application. For this reason, if possible it is useful to prepare test cases early in the development cycle.

Configuration management (CM) covers the tools and processes used to control, coordinate and track code, requirements, problems, designs, documentation, change requests, tools, patches, compilers, libraries, who makes the changes and changes made to them