NetD

QA training
Kannan J and Bhaskar B.S

Need For testing

Any Software Must be Tested to uncover as many as errors as possible before delivery to customer. Testing should be Designed through a series of Test cases to find likelihood of errors.

Start and End

When Testing Starts? -- As soon as the Initial version of FS is ready. When Testing Ends? -- As long as the product exists, testing never ends.

Types Of testing
White Box -- Exercise the internal logic of Software Components. Black Box -- Exercise the input and output domains of the program. -- Functional testing -- Integration testing -- System Testing -- Performance Testing -- Stress Testing

Test Planning
Preparation of a Test Plan -- refer RFC -- Refer FS Planning testing -- When to Start Testing -- When to test performance -- Code COverage

Test Plan Document

Contents -- Owner Details -- Revision history -- Topology Details -- Resource Requirement -- Test cases -- CLI details -- Comments and AIs

Black Box testing

Functional Testing Integration testing Performance Testing System Testing

Testing Manual vs Automations

Manual Testing -- time consuming and prone to error. Automation Testing -- Saves Time, Accuracy.

Manual Testing
Certain types of tests like performance, Load , Resync tests are Difficult to Automate. Manual testing must be minimal in a testing environment.

Automation testing
Test cases will be Automated using tools like Winrunner, Load Runner, TCL. -- Time Saving, avoids manual interaction and enhances test accuracy.

Tools Used for Testing

ATAL Spirent NATS

Bugs
When ever an issue is seen, should be filed in Bugzilla, (bugzilla.netd.com) Components owners responsibility to track the bug. Once bug is fixed , it must be verified and status should be changed accordingly. No two issues should be clubbed in One Bug.