Answer Posted / rajendra prasad

Configuration Management:
Definition-1:
Software configuration management (SCM) is the task of
tracking and controlling changes in the software.

Definition-2:
"Set of activities designed to control change by
identifying the work products that are likely to change,
establishing relationships among them, defining mechanisms
for managing different versions of these work products,
controlling the changes imposed, and auditing and reporting
on the changes made."

In a generic way Management includes ADD,Update,Delete
Repleace operations.

software development process is a Team activity, All team
members will share the work to develop the software.

The development activity may take from months to years based
on complexity and size of the project.

To explain configuration management indeatail,eg:
A software product is under development, so some 25 people
are working for that project.

These 25 people may include developpers,Development leads,
Project managers,Test Leads,Test engineers..etc.

All people should have some common repository(Like library)
to keep the documents,Code available for remaining team.
Ofcourse based on their designnation different people will
have different access permisions(Read/Write).

This repository will consists different folders and sub
folders.
>$
Deveopment
-Project Plans
-Design Documents
-Code
QC
-Test Plan
-Test Case Documents
-Traceability Doc
-Test Results
-Test Results Build QC 1.0
-Test Results Build QC 1.1
-Test Results Build QC 1.2....etc
For testing people will have access permission to view the
Requirement document folder(Read Only),
Test Plan folder(Read,write permissions)
Test Case documents folder(Read,write permissions)
Test Results documents folder(Read,write permissions)

If three test engineers(A,B,C) are working on this project
all three people will have acccess to read and write
testcases.

'Test Engineer A' prepared Test Case document and kept in
configuration management system.
Keeping the Documents in configuration management system is
called as 'Checkin' of documents
These Test Case document will be available for remaining
test Engineers B,C.
If Test Engineer 'B' Want update the existing testcase or
add some new test cases the then 'B' check the document 'B'
check out the document and Makes changes to it and
Again 'Checkin''s the updated document.
When 'B' check in the document 'configuration management'
will ask to enter some information regarding the updation
details.

Remaining i will explain later
byee
Rajendra Prasad
rajendra_penumalli@yahoo.com



If Tester A modified the

If you are handling a product testing and if there are around 100 test cases and in them few test cases are failed then at the end of the day how will you treat whether the product is pass/fail.? consider the failed test cases are in functional requirements.

1993

---

Why it is recommended to add verification checks to your all your scenarios?

2076

---

Can anyone tell me, What is wound fixing?

2558

---

How to do manual testing of a E-insurance project (end to end process)

3318

---

what are the status have in QC(Test Management Tool). and how you report?

1905

---

What is showstopper defect?

1157

---

what are the typical problems in web testing?

1242

---

Test Cases For Router&Switch

2576

---

functional testing test cases for transfer funds ?

1617

---

what does 80hz refresh rate indicates?

2868

---

date format and we should 8 digits - not accepted only /accepted write how many in test cases in the date format valid , and in valid

1461

---

Why is it impossible to test a program completely?

1513

---

What is mutation testing & when can it be done?

1121

---

You may undergone many projects. Do all the projects match up with customer’s expectations?

1125

---

What do you do (with the project staff) when the schedule fails?

2056

---