Database Question

What is As the difference among “dropping a table”, “truncating a table” and “deleting all records” from a table.
Answer :
Drop Table - will remove the existence of the table from the database along with its data and structure and all the constraints. The table will be no longer available.

A Truncate Table - will remove all the rows (only the rows) from a table. it will not delete the table. Its a DDL statement that means the deleted rows cannot be reverted back by ROLLBACK statement;

Delete Table - is a DML statement which will delete rows from a table according to the matching criteria mentions in the ‘where’ clause. And these rows can be reverted back by ‘ROLLBACK’ statement if ‘COMMIT’ is not fired.

What are the Large object types supported by Oracle?
Answer :
These are the large object type supported bye oracle
• CLOB and LONG for large fixed-width character data
• NCLOB for large fixed-width national character set data
• BLOB and LONG RAW for storing unstructured data
• BFILE for storing unstructured data in operating system files

What are the different types of joins?
Answer :

Different Types of Joins-
Inner Join
Outer Join - Right Outer Join & Left Outer Join
Cross Join

What is snapshot log?
Answer :

It is a table that maintains a record of modifications to the master table in a snapshot. It is stored in the same database as master table and is only available for simple snapshots. It should be created before creating snapshots.

Explain the difference between MyISAM Static and MyISAM Dynamic.
Answer :
In MyISAM static all the fields have fixed width. The Dynamic MyISAM table would include fields such as TEXT, BLOB, etc. to accommodate the data types with various lengths. MyISAM Static would be easier to restore in case of corruption, since even though you might lose some data, you know exactly where to look for the beginning of the next record.

How can you Enforce Referential Integrity in snapshots?
Answer :

Time the references to occur when master tables are not in use. Perform the reference the manually immediately locking the master tables. We can join tables in snapshots by creating a complex snapshots that will based on the master tables.

What is Two-Phase Commit?
Answer :

Two-phase commit is mechanism that guarantees a distributed transaction either commits on all involved nodes or rolls back on all involved nodes to maintain data consistency across the global distributed database. It has two phase, a Prepare Phase and a Commit Phase.
What is a cluster Key?
Answer :
The related columns of the tables are called the cluster key. The cluster key is indexed using a cluster index and its value is stored only once for multiple tables in the cluster.

What is Read-Only Transaction?
Answer :

A Read-Only transaction ensures that the results of each query executed in the transaction are consistent with respect to the same point in time.

What is Rule-based approach to optimization?
Answer :

Choosing an executing plan based on the access paths available and the ranks of these access paths.

What are constraints? Explain different types of constraints?
Answer
# 1 constraint is a rule which can not be voilated by end users.
Different types of constraints are available.They are:-
1)default constraint:-which is used to define a default
value.
2)primary key:-the key which does not allows duplication
and null values.
3)foreign key:-the key used to refer primary key defined
field in another table and it allows duplication.
4)null:-which allows NULL values.
5)not null:-which does not allows NULL values.
6)unique key:-which does not allows duplication but allows
NULL values.

----------------------------
Testing

Question Find the Cyclometric complexity on the following pseudocode


Do while records remain
read record;
if record field#1=0
then process record;store in buffer;
incremental counter;store in file.
reset counter;end if end do

please let me know the procedure too.

Q.Find the Cyclometric complexity on the following p seudocode Do while records remain read record; if record field#1=0 then process record;store in buffer; incremental counter;store in file. reset counter;end if end do please let me know the procedure too.
Answer
# 1 Listen i will tell u a basic funda:

Cylometric complexity is THE NO. OF LOOPS + 1

so in the question u have to check how many loops r present.

if its 1 then the ans is 2
if its 0 then the nas is 1
-----------
Answer
# 2 The answer for this is 3

3 formula's to calculate Cyclomatic complexity. You can
choose either of them...
C.C = No of bounded regions +1
C.C = No of edges - No of nodes +1
C.C = No of predicate Nodes +1

Now let's consider the first formula to calculate as the
rest 2 diagrams require flow graphs to be drawn.

Do while loop forms 1 bounded region
and IF condition forms 1 bounded region.

So as per this formula, C.C = No of bounded regions +1
2 + 1 = 3
-------------
What is Retesting?
Answer
# 1 Executing the same test cases on the same build but with
different inputs..

Answer
# 2 re execution of the test cases on the same build with
diffrent set of inputs

Answer
# 3 re executing the cases to get the confirmation that defects
are reproducable

What is defect leaking and defect release
Answer
# 1 While verifying the defect if it has been found tobe not
fixed, then it is called defect leaking.

If it has been fixed, then the defect is said to be release

Answer
# 2 when a version is released say ex:version2.0 and is any
modifications have been made to this version and named to
version 2.1 and the u find any (small) defect in the new
version which was left in 2.0 the tht is called defect leakage

A Succesful testcase Means..?
Answer
# 1 it should cover the functionality,it doed not contain if
staement,high probabilty of finding defect

Answer
# 2 A good testcase should satisfy the following two basic
requirements:
1.It should cover all the requirements as mentioned in the
srs
2.For each requirement different scenarios that are
possible should also be mentioned.

Answer
# 3 should cover functionality
should be easy to understand
should be maintanable

Answer
# 7 a Successful test case uncovers as an yet undiscovered
defect

Answer
# 8 to cover all functionality and intended to find bugs

Question Suppose " You are given a build with 5 modules to test as
per the Customer request after finalization of SRS, But the
SRS contains only documentation about 4 modules. On what
basis you will continue the testing of 5th module." ?

Answer
# 1 is developer problem

Answer
# 2 If it is not in SRS, it is bug. Any extra sec. is a bug
also.

Answer
# 3 I think we do Adhoc Testing. Upto 4 modules we first check
the functionality. After that we do the Adhoc on the 5th
module.
Generally we do Adhoc Testing, when there is no clear
specifications or when the time is less.

Answer
# 4 SRS is prepared based on requirements. Even SRS is not
there and have requirements, we analyze the requirements
first, Take the inputs from domain experts,end users.
Consolidate and prepare the SRS on our own and will send
the same for customer approval. based on feed back we can
go with testing.

Answer
# 5 Along with the Build release to the Testing team
Devolopment people releases Build release document, by
studing the release document we are going to conduct
testing on 5 th module.

Answer
# 6 if srs is available prepare test cases and to conduct
formal testing
if SRS is not available in this time we conduct adhoc testing.



Question Testing of Non-Functional requirements does not involove
a) Performance tests
b) Reliability tests
c) usability tests
d) Configuration tests

Answer
# 1 Configuration test


Answer
# 2 reliability tests & configuration tests

Answer
# 3 non functional reuirements includes all ie. performance,
reliability , usability & configiration tests.

Answer
# 4 all are non functional req. i guess...well done poonam

Answer
# 5 Reliability , Usability and Configuration comes under
Functional requirements, and Performance comes under non
functional requirements..

Answer
# 6 In Non-functionality requirements .We consider 1)performance
2)security that's it

What is metrics? explian the type of metrices.
Answer
# 3 Metrics are generally classified into 2 types
1. Process metrics
2. Product metrics
b a metric used to measure the haracteristic of the
methods, techniques and tools employed in eveloping,
implementing and maintaining the software system.


Product metric: a metric used to measure the characteristic
of the documentation and code. The metrics for the test
process would include status of test activities against the
plan, test coverage achieved so far, amongst others. An
important metric is the number ofdefects found in internal
testing compared to the defect found in customer tests,
which indicate the effectiveness of the test process itself.

Answer
# 4 Metrics meaures the strength of testing process

In otherwords it measures how much percentage of testing is
complted

types of metrics

Functional covreage

Softwate release metric

Error discovery rate
stability trend chart

what are the Levels of testing?
Answer
# 1 1. Unit Testing
2. Integration Testing
3. System Testing
4. Acceptance Testing
5. Regression Testing

Answer
# 2 there r 4 levels of testing
level 0 :: Sanity Testing test whether build is testable
or not
level 1 :: Unit testing, Integraion Testing, System Testing
level 2 :: Regression Testing
level 3 :: Final Regression testing or Postmartom Testing

Answer
# 3 There are only 4 levels of testing

1. Unit Testing
2. Integration Testing
3. System Testing
4. User Acceptance Testing

Answer
# 4 1.unit testing
2.Integration testing
a)Top down integration testing
b)Bottom up integration testing
c)Big Bang integration testing
d)Isolation integration testing
e)Incremental integration testing
3.System testing
4.Acceptance testing.

Answer
# 5 Levels of testing
1.Unit testing
2.Module testing
3.Interation testing
a)Top down integration testing
b)Bottom up integration testing
c)Big Bang integration testing
d)Isolation integration testing
e)Incremental integration testing
4.System testing
5.User acceptance testing

What kinds of testing have you done?
Answer
# 1 I performed Installation testing, browser compatability
testing, regression testing, parallel testing.

Answer
# 2 Testers can perform Balck box testing,Grey box
testing,Smoke testing,Sanity testing,endurance
testing,automation testing,volume testing,Database
testing,Stress testing,End-end testing,alpha testing,adhoc
testing,concurrency testing ....List will not end!!!!!!!

Answer
# 3 Tester can perform Black box testing,GUI testing,DataBase
testing,Integration(Tester+Developer)System and UAT.As per
Client requirements.

Answer
# 4 Moreover testers perform sanity testing, black box,
regression, performance, volume, system testing and installtion.

Answer
# 5 I would like to add something here

Black Box & White box testing are two approaches of testing
Most commonly every tester perform
1.Functional testing
2.Regression testing
3.Re-testing
4.Sanity testing
5.Compatibility testing
6.UI testing
7.Exploratory tesing (this is depending upon the type of
project)
8.end to end testing
9.adhoc testing
10.Installation testing

Answer
# 7 Kinds of testing means:

1. Static testing & Dynamic testing.
2. Structural testing & Functional testing.
3. Automation testing & Manual testing.

Testers will do only:

Dynamic testing
Functional testing
Manual testing

what type of documents can u prepare during Testing?
Answer
# 1 Test case document, Bug report, Status reports, Tracebility
Matrix, Use cases, Metric preparation, Release report

Answer
# 2 1.Test Plan : A formal test plan is a document that
provides and records important information about a test
project, for example: Resources, Schedule & Timeline, Test
Milestones, Use cases and/or Test cases
2.Test Case: A set of test inputs, execution conditions and
expected results.
3.Test Data: The actual (set of) values used in the test or
that are necessary to execute the test.
4.Test Scripts: is used to test a particular functionality
(business rule). It may consist of 1 or more Test Cases.
5.Test Log: A chronological record of all relevant details
about the execution of a test
6.Bug Reports: Contains a summary of the bug, its priority
and other details regarding the bug.

Answer
# 3 BRD business requirment document.
srs system requirment specifications.
frs functional requirment specifications,
Test plan: it include what to test,when to test ,where to
test, whom to test,how to test.
test cases : functionality to be test
defwct reporting :
bug report :

Answer
# 4 Here I ma giving all the documents,which are using in our
project and the authorized person,who is preparing them.It
varies from company to company.

Project Plan:Prepared by PM.
QA-Project Plan:Prepared by QA Manager
Test Reports:Generally prepared by Team lead for every
release.
Software Metrics: Team Lead
Module based Test Plan: Testing engineer
Test Results: Test Engineer
Testcase document: Test Engineer
Defect Matrix: Prepared by Team Lead
Traceability Matrix: Team Lead or team member
Bu Reports: Prepared by test engineer.

Define Brain Storming and Cause Effect Graphing? With Eg?
Answer
# 1 Hi...........
BS:
A learning technique involving open group discussion
intended to expand the range of available ideas
OR
A meeting to generate creative ideas. At PEPSI Advertising,
daily, weekly and bi-monthly brainstorming sessions are
held by various work groups within the firm. Our monthly I-
Power brainstorming meeting is attended by the entire
agency staff.
OR
Brainstorming is a highly structured process to help
generate ideas. It is based on the principle that you
cannot generate and evaluate ideas at the same time. To use
brainstorming, you must first gain agreement from the group
to try brainstorming for a fixed interval (eg six minutes).

CEG :
A testing technique that aids in selecting, in a systematic
way, a high-yield set of test cases that logically relates
causes to effects to produce test cases. It has a
beneficial side effect in pointing out incompleteness and
ambiguities in specifications.

What is software development Life Cycle (SDLC)? where exactly the Testing activity begin in SDLC?
Answer
# 1 SDLC is a framework for understanding and developing
information and software succesfully.

Answer
# 2 SDLC is a framework for understanding and developing
information and software succesfully.

Testing activity begins right from the requirement analysis
phase.




For Web Applications what type of tests r u going to do .. tell me the Importent ones..
Answer
# 2 The following are the tests need to be done for Web
application.


Static Testing
Dynamic Testing
Navigation Testing
Compatabilty Testing
Functionality Testing
Link Testing

Answer
# 3 for an web application we need 2 check

URL of appl
navigation(Normal links,broken links_
scalability
reliabilty(recovery testing)
usability
compatbility
forms,cookies

Answer
# 4 for web application mainly tests as follows

userinterface means everyone understand the application is
mportant
funcationality
navigation
performence means speed of acces is imp
links

Answer
# 5 Functional Testing
Smoke Testing(for UI and API's-- Through Automation tool)
Regression Testing
Batch Process Testing(for simulators)

---------
Web-based applications present new challenges, these challenges include:
- Short release cycles;
- Constantly Changing Technology;
- Possible huge number of users during initial website launch;
- Inability to control the user's running environment;
- 24-hour availability of the web site.

The quality of a website must be evident from the Onset. Any difficulty whether in response time, accuracy of information, or ease of use-will compel the user to click to a competitor's site. Such problems translate into lost of users, lost sales, and poor company image.

To overcome these types of problems, use the following techniques:
1. Functionality Testing
Functionality testing involves making Sure the features that most affect user interactions work properly. These include :
· forms
· searches
· pop-up windows
· shopping carts
· online payments

2. Usability Testing
Many users have low tolerance for anything that is difficult to use or that does not work. A user's first impression of the site is important, and many websites have become cluttered with an increasing number of features. For general-use websites frustrated users can easily click over a competitor's site.

Usability testing involves following main steps
· identify the website's purpose;
· identify the indented users;
· define tests and conduct the usability testing
· analyze the acquired information

3. Navigation Testing
Good Navigation is an essential part of a website, especially those that are complex and provide a lot of information. Assessing navigation is a major part of usability Testing.

4. Forms Testing
Websites that use forms need tests to ensure that each field works properly and that the forms posts all data as intended by the designer.

5. Page Content Testing
Each web page must be tested for correct content from the user perspective for correct content from the user perspective. These tests fall into two categories: ensuring that each component functions correctly and ensuring that the content of each is correct.

6. Configuration and Compatibility Testing
A key challenge for web applications is ensuring that the user sees a web page as the designer intended. The user can select different browser software and browser options, use different network software and on-line service, and run other concurrent applications. We execute the application under every browser/platform combination to ensure the web sites work properly under various environments.

7. Reliability and Availability Testing
A key requirement o a website is that it Be available whenever the user requests it, after 24-hours a day, every day. The number of users accessing web site simultaneously may also affect the site's availability.

8. Performance Testing
Performance Testing, which evaluates System performance under normal and heavy usage, is crucial to success of any web application. A system that takes for long to respond may frustrate the user who can then quickly move to a competitor's site. Given enough time, every page request will eventually be delivered. Performance testing seeks to ensure that the website server responds to browser requests within defined parameters.

9. Load Testing
The purpose of Load testing is to model real world experiences, typically by generating many simultaneous users accessing the website. We use automation tools to increases the ability to conduct a valid load test, because it emulates thousand of users by sending simultaneous requests to the application or the server.

10. Stress Testing
Stress Testing consists of subjecting the system to varying and maximum loads to evaluate the resulting performance. We use automated test tools to simulate loads on website and execute the tests continuously for several hours or days.

11. Security Testing
Security is a primary concern when communicating and conducting business- especially sensitive and business- critical transactions - over the internet. The user wants assurance that personal and financial information is secure. Finding the vulnerabilities in an application that would grant an unauthorized user access to the system is important.

Following is the strategy we used in one of my projects:
1. From the requirements, list the priorities of testing.
2. Use a Link Checker to check all the broken text and image links. This will alert you on missing or broken links but not links that have been pointed to the unintended locations/files. But ignore such links for now this is just one of the cursory checks. Report the results.
3. Collect as many scenarios of real users browsing your site. If you are testing an already existing site you can get them from the site Stats. These will probably cover all your existing user base. If your site needs to target additional user base that is a whole other task.
4. Test using the scenarios.
5. From your testing priorities, list the test cases not touched in your previous test scenarios. If you want a complete list or have time to create one, just go ahead or else you can also list them and note the result from your tests earlier in here. We just listed a short description of each test case, it's input and output. It'll be helpful to record your results if you've a column in there to record your results when testing.
6. Start testing using the test cases and record the results.
7. Prioritize and Report the defects. If you don't have time for testing, there might not be sufficient time to fix them all and re-test the defects either. Prioritizing them will help fix at least the major bugs and/or issues. The rest will be fixed or ignored depending on their priority and your project deadlines.

What are the test methodologies??
Answer
# 1 Test Methodolgies defines how to approach the
testing .project type,system domain,risks,at which phase
what type of testing occurs,

all these comes under Methodology

What are the contents in "Requirements Traceability Matrix" not in " Test Responsibility Matrix"?
Answer
# 1 Contents of Requirements Traceability Matrix / RTM :

Release Name
Test Case Name
High level design
Low Level Design
Test Case Execution
Automation Execution

Difference between regression testing and re testing?
Answer
# 1 Retesting- Re test the defects after fixed.
Regression testing-- Nothing but retest, After fix the
defects we are checking the functinality,if the fixed
defect is effected to another functionality.

Answer
# 2 Retesting : Testing the application on the same built
soppose tester found the bugs and developer fixed it.
tested the fixed issues on the same built is called
retesting.
Regression: Testing the application on the different built
Suppose: if the tester found the bugs, and Developer fixed
it and they relised the new version of the build. so
testing on the new version on the built is called Regerssion
Testing

Answer
# 3 re testing:testing the build with multiple test data
regression testing:if the tester find any defect he /she
inform this defect to development team.developement team
fixes that bug, aagin send to the testing team for testing
again whether bug is fixed or not,or the newly developed
build giving any side affects to other modules or not.

Answer
# 4 Re Testing: Once the Bug is fixed Tester has to test the
same bug with multiple number of times with different data
and different scenario. Also once tester find the bug he
has to test multiple number of times bcoz whether the bug
is reproduceable or not.

Regression Testing: Once the Bug is fixed tester has to
test whether bug is fixed or not also test whether the
impact of the bug is shows in other application

What is the diffrence between BUILD & RELEASE ?
Answer
# 1 Difference number one:Builds refer to software that is
still in testing, release refers to software that is
usually no longer in testing.

Difference number two: Builds occur more frequently;
releases occur less frequently.

Answer
# 2 Generally build is a inegrated module,which contains the
fixes for your previous builds bugsGenerally we will
recievie the builds in daily basis,weekly basis.

Once we completed the testing on our software,before we
rolling out that software to our client,we will select a
final build,which is almost defect free and we will take
that build as release build.That release build will be
introduced in the market for end-users.

What is risk analysis,what type of risk analysis u did in u r project
Answer
# 1 hi.................(Must say u have a very good question )
Risk Analysis :
A systematic use of available information to determine how
often specified events and unspecified events may occur and
the magnitude of their likely consequences

OR

procedure to identify threats & vulnerabilities, analyze
them to ascertain the exposures, and highlight how the
impact can be eliminated or reduced

Types :

1.QUANTITATIVE RISK ANALYSIS
2.QUALITATIVE RISK ANALYSIS

what is test case? what it consists? what are the types of test cases?
Answer
# 1 Test Case is a document that describes the input or action
or event and expected response to determine the feature of
the application is working correctly. It contains Test case
No: Action/Input and Expected and Actual Result and Status
(Pass/Fail).


Answer
# 2 Test case is a document specifying inputs, predicted
results, and a set of execution conditions for a test
item.We can name test cases as system test
cases,integration test cases,Unit test cases (that include
validations)

Answer
# 3 Sharavati,
The Test cases naming which you have mentioned here is said
the be levels of testing in testing life cycle of a
software. Hence you cannot name/catogorize the test cases.

Answer
# 4 Test case is a document.It contains inputs,outputs and
outcome .There are three types of test cases
they are
1)Business logic based testcases
2)Input domain based testcases
3)user interface based testcases

Answer
# 5 Test case is a document.It contains inputs,outputs and
outcome .There are three types of test cases
they are
1)Business logic based testcases
2)Input domain based testcases
3)user interface based testcases

Answer
# 6 For me test cases is a document which describes ,
What is we r going to test ,i.e (test area)
followed by test description ,then by the test steps , then
the expected result ,actual result , status(pass/fail_)

Answer
# 7 Test Case:
Definition: To verify the possible values for the
attribute.

It Cosists:
positive and negative values for the attribute

Types:
GUI test case
Functional test case
System level test case

Answer
# 9 Test case is descrption f what is to be tested, what the
data to be used ,what are the actions done to check the
actual results against expected result



What is the difference between QC and QA?
Answer :
Quality assurance is the process where the documents for the product to be tested is verified with actual requirements of the customers. It includes inspection, auditing , code review , meeting etc.
Quality control is the process where the product is actually executed and the expected behavior is verified by comparing with the actual behavior of the software under test. All the testing types like black box testing, white box testing comes under quality control.
Quality assurance is done before quality control.
What is a scenario?
Answer :
A scenario defines the events that occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions to be performed, and the machines on which the virtual users run their emulations.





What is Difference betweem Manual and Automation Testing?
Answer :
This answer is quite simple, Manual is when user needs to do many things based on the test case specified, say like click some tab and check if the tab is working fine or click on a particular URL and check if the web site specified opens.

The above stuff can also be done automatically, i.e. through some automated tools like Winrunner , Silk Test etc the things can be automated , so user just has to trigger the tool and the tool will take care of executing , only thing needed is we need to know how to make the testcases automated through that tool which is not very difficult.

What is L10 Testing?
Answer :
L10 Testing is Localization Testing, it verifies whether your products are ready for local markets or not.

What is I18N Testing?
Answer :
I18N Testing is “Internationalization testing”
Determine whether your developed product’s support for international character encoding methods is sufficient and whether your product development methodologies take into account international coding standards.

What is SEI? CMM? CMMI? ISO? IEEE? ANSI?
Answer :

SEI = ‘Software Engineering Institute’ at Carnegie-Mellon University; initiated by the U.S. Defense Department to help improve software development processes.
CMM = ‘Capability Maturity Model’, now called the CMMI (’Capability Maturity Model Integration’), developed by the SEI. It’s a model of 5 levels of process ‘maturity’ that determine effectiveness in delivering quality software. It is geared to large organizations such as large U.S. Defense Department contractors. However, many of the QA processes involved are appropriate to any organization, and if reasonably applied can be helpful. Organizations can receive CMMI ratings by undergoing assessments by qualified auditors.

Level 1 - characterized by chaos, periodic panics, and heroic efforts required by individuals to successfully complete projects. Few if any processes in place; successes may not be repeatable.
Level 2 - software project tracking, requirements management, realistic planning, and configuration management processes are in place; successful practices can be repeated.
Level 3 - standard software development and maintenance processes are integrated throughout an organization; a Software Engineering Process Group is is in place to oversee software processes, and training programs are used to ensure understanding and compliance.
Level 4 - metrics are used to track productivity, processes, and products. Project performance is predictable, and quality is consistently high.
Level 5 - the focus is on continouous process improvement. The impact of new processes and technologies can be predicted and effectively implemented when required.

ISO = ‘International Organisation for Standardization’ - The ISO 9001:2000 standard (which replaces the previous standard of 1994) concerns quality systems that are assessed by outside auditors, and it applies to many kinds of production and manufacturing organizations, not just software. It covers documentation, design, development, production, testing, installation, servicing, and other processes. The full set of standards consists of: (a)Q9001-2000 - Quality Management Systems: Requirements; (b)Q9000-2000 - Quality Management Systems: Fundamentals and Vocabulary; (c)Q9004-2000 - Quality Management Systems: Guidelines for Performance Improvements.

To be ISO 9001 certified, a third-party auditor assesses an organization, and certification is typically good for about 3 years, after which a complete reassessment is required. Note that ISO certification does not necessarily indicate quality products - it indicates only that documented processes are followed.

IEEE = ‘Institute of Electrical and Electronics Engineers’ - among other things, creates standards such as ‘IEEE Standard for Software Test Documentation’ (IEEE/ANSI Standard 829), ‘IEEE Standard of Software Unit Testing (IEEE/ANSI Standard 1008), ‘IEEE Standard for Software Quality Assurance Plans’ (IEEE/ANSI Standard 730) etc

ANSI = ‘American National Standards Institute’, the primary industrial standards body in the U.S.; publishes some software-related standards in conjunction with the IEEE and ASQ (American Society for Quality).

Other software development/IT management process assessment methods besides CMMI and ISO 9000 include SPICE, Trillium, TickIT, Bootstrap, ITIL, MOF, and CobiT.

What is documentation change management?
Answer :
Documentation change management is part of configuration management (CM). CM covers the tools and processes used to control, coordinate and track code, requirements, documentation, problems, change requests, designs, tools, compilers, libraries, patches, changes made to them and who makes the changes

What is the role of documentation in QA?
Answer :

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

How do you perform integration testing?
Answer :
First, unit testing has to be completed. Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements. Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team.
Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.

What is clear box testing?
Answer :
Clear box testing is the same as white box testing. It is a testing approach that examines the application’s program structure, and derives test cases from the application’s program logic.

What is closed box testing?
Answer :
Closed box testing is same as black box testing. Black box testing a type of testing that considers only externally visible behavior. Black box testing considers neither the code itself, nor the “inner workings” of the software.

What is open box testing?
Answer :
Open box testing is same as white box testing. It is a testing approach that examines the application’s program structure, and derives test cases from the application’s program logic.

What is ‘Software Quality Assurance’?
Answer :
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’.

What is Security Testing?
Answer :
Security Testing

Application vulnerabilities leave your system open to attacks, Downtime, Data theft, Data corruption and application Defacement. Security within an application or web service is crucial to avoid such vulnerabilities and new threats.

While automated tools can help to eliminate many generic security issues, the detection of application vulnerabilities requires independent evaluation of your specific application’s features and functions by experts. An external security vulnerability review by Third Eye Testing will give you the best possible confidence that your application is as secure as possible.

Q: How do I test a database?A: As far as I know there are four different things that could beconsidered database testing1) using the database as a repository for some user-generatedfront-end activity (client-server)2) using the database as a repository for some application-generatedactivity (transaction logging)3) database migration (bringing one repository from one schema toanother or merging two or more schemas)4) database development (you work for Oracle, MySQL, or a company thatmakes databases)Which one are you trying to do?How to Thoroughly Test a Data WarehouseAuthor(s): Rebecca Cooper/Suellen Arbucklehttp://www.stickyminds.com/r.asp?F=DART_5941Temporal Data Integrity ValidationAuthor(s): Doron Drusinskyhttp://www.stickyminds.com/r.asp?F=DART_5938Testing Merged DatabasesAuthor(s): Bernie Berger/Lawrence NuanezSTQE Issue: Nov/Dec 2002 (Vol. 4 Issue 6)http://www.stickyminds.com/r.asp?F=DART_6181This article requires a PowerPass. It is summarised in the abstract,which I'll paraphrase for you here:This addresses four different problems that have to be overcome in adatabase merger:1) duplicate records (The challenge of duplicate records);2) mismatched columns (Ways to check for mismatched column definitions);3) data corruption (Tips for finding corrupt data);and 4) front-end assumptions (How to verify front- and back-end congruence).

How can u do regression testing tell me procedure?

Answer
# 1 Regression test will be done when we got modified build there we execute test cases to determine whether defects closed or not? or checking 2 ensure that resolved bug has made any impact
on the remaining part of code

Answer
# 2 Regression Testing is as discussed in above answer is done
after the first build release, and in regression testing we
test if the bugs that exited in the Build are actually fixed
or not, we also apply testcases for new requirements (if
any) to check if the system is working fine.

Answer
# 3 Regarding the regression testing procedure, it is same as
testing, we just re-run all those test that were previously
run, but this time we make sure that the test cases match
the new chnages, or new requirements that were not there in
the system.

Answer
# 4 Regreesion testing is nothing but whenever we find out the
bug , it has to be fixed ,given to developers they will fix
the bug , this is known as regression testing
Answer
# 5 Regression Testing-"Testing to ensure that introduction of
new functionality has not affected existing functionality"

Answer
# 6 Whenever tester gets the next fixed build:
1)He tests for the Fixed Bugs.
2)Test the whole application to check whether these fixes,
have not introduced new bugs.
3)If there are some update in the application, then test
cases need to be updated , and executed the same.

All of the above steps used, while doing regression testing.

Answer
# 7 Reexecution of testcases on modified form of build is
called regression testing.

Answer
# 8 regression testing:when ever the bug is fixed from
developement team we can verify whether the bug is fixed or
not and their related functionality is also working fine or not.