Since there are many CFDs comes up in the old builds' GUI, so need to setup a ATM testing framework to improve the product's quality.
<actually it is because a beautiful mistake by other stuff.... and i have to pick it up, but it is a good opportunity to touch atm testing>
Main tools : selenium 2(webdriver)+ java(eclipse)+testng
Difference: I have to say, communication product GUI ATM has some difference compared with internet GUI ATM .
**** Communication device have to check CLI(linux) results***
Now here are the good lessons drawn from my setbacks in the past.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Before setting up the ATM framework, the following conditions shall be met simultaneously:
(1) Build requirements will not change frequently
(2) Relatively long life of the project
(3) ATM scripts can be reused.
Why i list them here? yes, i suffered a lot from here since i didn't aware of this at the begging of the job.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Find tips here:
1. arrange the case number reasonably
This is a necessary condition when your cases has some dependence, or you want your cases more easily to maintain.
e.g. Packet-A a01
a02
a03...
Packet-B b01
b02
b03
2. add "wait" in every jumped webpage