3. Examples
Studying for an exam
Multiple subjects in a semester
Working together as a team – Towards a
common goal
Our Brain – All in all
“No super computer has reached the
processing capabilities of a human brain”
4. Today…
“We will try to bridge the Tech and Non Tech
understanding of Parallel Computing”
Tech – Java
Non Tech – Self and Team Work
6. Processing
Serial Run – One after the other – Semester
Exam – One exam a day
Parallel Run
Threading – Reading a book
Executors – Working as a team
Fork Join – Working as an efficient team
8. Threading
See
Read
Underline important points
Understand
Remember
“Similarly, a computer process can spawn
threads to compute a problem in parallel”
9. Executors – Java 6
Single Core vs. Multi Core
How to use multi core
Thread Pooling
“Working together as a team”
10. Fork Join – Java 7
Divide and Conquer
Use multiple cores
Special Algorithm – WORK STEALING
“Working as an efficient team”
11. Work Stealing
Steal the work from cores that are busy
Full utilization of CPU
“If you are free,
share the work load of your team mates”
12. Practical
100 tasks need to be run on a Quad Core machine
Following ways
Serial
Parallel – Executors [4 & 16 threads]
Parallel – Fork Join
Observe the CPU Chart
Note
Practical code - Parallel.zip available
mfinfiles02/Public_Engineering_India/_Device_Team/Senthil/Parallel.zip
Study jDevSim code [jDevSim, jAppDownload, jGcmServer] –
http://mfinsvn/repo-mirror/devices/trunk/JavaDeviceSimulator
13. CPU Chart – Serial
122.777 seconds
10 to 15% CPU Utilization
14. CPU Chart – Executors – 4 Threads
36.624 seconds
~50+% CPU Utilization
15. CPU Chart – Executors – 16 Threads
16.842 seconds
Almost 100%
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources
New product Version releases
Test Plans, and test cases development and test execution
Regression, new features & Performance testing is performed
Comprehensive Release documentation- Field Release letter
Maintenance releases (Post Production releases)
Primarily major or high priority bug fixes comprise in this release
The approach (1) simulate the defect (2) apply the fix (3) validate the fix (4) test the impacted areas
Comprehensive Release documentation- Field Release letter
General Availability (GA) in Mformation Context
Definition: As per defined and agreed requirements, the MSM software operates on a common understanding as to what is included and/or excluded from a release
GA decision Process: A panel of Mformation stakeholders across groups (PDM, Engineering & Deployment) review and decide go/no-go decision for GA release based on the open P1 blockers, P1 majors and P1 & P2 Normal defects in the product as on the date of release to field
GA qualification of a release
New feature Testing: New test cases will be developed against the defined requirements and scope of the feature. This will be targeted for a single test pass during QA cycle.
Regression: All the pre-existing MSM applicable features in a particular release will be targeted for a single test pass. This implies that all deprecated features from the product will not be tested.
Product Field release letter is a comprehensive document that describes all aspects of a release
The number of test cases will depend on the definitive content of new features and the regression suite.
Total TCs as on date is about ~4500+ (Core MSM features + Generic features applicable to majority of the operators)
Upgrade process
Upgrades are applicable for existing customers only
Upgrade path & scripts are seamless from MSM version 9.x onwards to latest targeted release. This is verified by MF QA during the GA release cycle
On a special request, MF QA performs customer specific upgrade testing with customer DB dump and verifies customer specific ATP
Question if arise on resources>>> As on date we have 3- QA resources