Difference between Level & Types of Software testing

One user asked this question, "In one interview interviewer ask me the level of Software Testing. I read one web site type of software testing are unit testing, black box testing, white box testing, etc. Also in one web site i read level of software testing is unit testing, integration testing, system testing. so it is level & type of software testing is same. If no, then please tell me the difference."
Answer:- Levels of testing and types of testing are not the same things.
**levels of testing depends on process and software development life cycle model followed for software development.
**Types of testing are what we test in a software.

Need clarifications on smoke testing???

hi friend...

I need some clarifications while performing smoke testing.I have some basic knowledge in smoke testing:

smoke testing:

"In software engineering, a smoke test generally consists of a collection of tests that can be applied to a newly created or repaired computer program. "

In software testing, a smoke test is a collection of written tests that are performed on a system prior to being accepted for further testing. This is also known as a build verification test. This is a "shallow and wide" approach to the application. The tester "touches" all areas of the application without getting too deep

1.Smoke test generally consists of a collection of tests?? What are the collection of test done while performing smoke testing?????

2.A smoke test is a collection of written tests that are performed on a system prior to being accepted for further testing...we need to write scripts to perform smoke testing, if it is so in what language and what is the use????

3.Can the smoke testing can be conducted to web based and windows based application????

4.The tester "touches" all areas of the application without getting too deep??? I am confused touching all the areas but without deeply how?????

I have posted the question in our geek forum under the category testing issues: Title need clarification on smoke testing

Looking forward to hear from you, that's why i have mailed you..

I am sorry if i have disturbed you??? but please help me out????? thousands of questions from my mind regarding this topic

 

I will be greatful to you...

Thanks
deepa

Configuration Management Tool

Configuration Management (CM) is a tool that is used to manage change. Let's say Rohit and Brijesh are both tech writers and both are working on updates to a technical manual. During a meeting, their manager assigns them each a section of the same document to update.

The technical manual is stored on a computer that both can access. Without any CM tool or process in place, a number of problems could arise. One possible scenario is the computer storing the document might be set up so that Rohit and Brijesh can not both work on the manual at the same time. This would slow them down considerably.

A more dangerous situation arises when the storage computer does allow the document to be opened by both Rohit and Brijesh at the same time. Here is what could happen:

1. Rohit opens the document on his computer and works on his section.

2. Brijesh opens the document on his computer and works on his section.

3. Rohit completes his changes and saves the document on the storage computer.

4. Brijesh completes his changes and saves the document on the storage computer.

CM systems are based on a simple idea: the definitive copies of your files are kept in a central repository. People check out copies of files from the repository, work on those copies, and then check them back in when they are finished. SCM systems manage and track revisions by multiple people against a single master set.

VSS, IBM ClearCase are most popular CM Tool use by software companies.

Benefits of Configuration Management Tool

• Optimize build times, improve reproducibility of builds

• Manage files, directories and other development assets across the lifecycle

• Work on the same code or release, more easily resolve conflicts, reduce confusion, and get more done in a short amount of time

• Manage and control software assets across the lifecycle

• Work on the same code or release, more easily resolve conflicts, reduce confusion, and get more done in a short amount of time

• Fast access to virtually any version of any element

• Continue development efforts while disconnected from the network, easily synchronize changes when reconnected to the network

• Allow developers to work in their preferred environment

• Trace the origin and detail of changes made to software assets, help meet compliance requirements

• Manage and control software assets across the lifecycle

• Support evolving organizational needs

-Rohit Sharma

er.s.rohit@gmail.com

When You Go For Interview and you are not selected

When You Go For Interview and you are not selected, then never underestimate your knowledge. You may be cut out because of knowledge but this is the case for a fresher only.

If you are an experienced professional, then only knowledge does not matters, there are lot of things, like

1) Your Domain of expertise.
2) Your Leadership qualities.
3) How quick learner you are?
4) What are the company requirements?
5) What is your expectation?
6) How much company can pay for that post?
7) How urgent is the opening?

So, its better to update yourself with new stuff, but it's bad to underestimate yourself.