Software Testing Technology Day01

Professor：[e-mail]
niel taylor
test software all the time.
test ruthlessly.don't leftuser bugs.
the existing code will be fine.deleiver good quanlity product.
major@Agile Methodologies.
@eCommerce
@adcanced internet system,software
@uiquitous mobile system,
@development
teeting == chanlenging,kitty;
projrct@Software SME:steel rolling mill;
project@FMEA:failure mode effects analysis;
#previously,purpopse+examples+kinds_of_test+test_tools+docu_testing ;
@blackboard: released before classes;via email;
----------------------------------------------------------------
Assessment: 60% examination 20% experiments+20% participation
----------------------------------------------------------------
Chapter 1:  Basic Concepts
 why use;why different ways;relationship on error,defects and failure;
 key steps;diff on static and dynamic ;
 capabilites for a person to be good ;
 ---    magically stop  ---
 --- what is bug --- :  cobol language
 problems prvent software from what we excepted for
 programming must be the process of putting bugs in -- dijkstra
 bug-free sofatware.
 @pay for the bugs
@purpose:Is_to_show[5] which one is more precise?[Thinking In Testing]
1> testing and debugging[looking for problems]
2> to show that the software works;
3> to show that the software doesn't work;best-social;
4> reduce the risk of using the software not to prove anything specific;
5> help all IT professionals develop higher software[mental discipline];

@how test?
@still have bugs?
@kind of bugs?
@the worst bug?thomas for my windows 10;safair for jpeg showed in browser;
 ----------- what if these softwares go wrong? ------------------
 @socail-media;online-payment-systment; televison os;
 @bank-system;everything goes off.
 @trafic-system;government-system;neu-clear system;
 @electrical-energy-management-system;
 @ct-machine system;lundon abulence system;mediacal systems;
@>>>>>> microsoft's experience;including private cloud solution;
cover 100 major product families;
3 divisions:1,platform + business + entertainent and device;
software testing engineers:35,000
----------------------------Concepts------------------------------
#Errors or mistakes:A problem during development.
#Defects or fault:A result of an error.
#Failures:The result when a fault executes.
#Incidents:The symptoms that indicates that indiciates that there is a fault.
#Test Cases:A set of input;identifiable test ID;review for further testing.
--------Relationship between software develpment and testing---------
###size and complexity of software ---->>>>> software lifecycle module !
#TESTING is also a vital part of this process.
@The Joel Test on how to better code.
[12 points] [to-do-list] [fewer means problem]
Companies like microsoft should run at 12 full-time.
1.use source control
2.make a build in one step[test right now build]
3.make daily builds
4.build a bug database
5.fix bugs before writing new code
6.have an up-to-date schedule,change around
7.have a specification
8.have quiet working conditions
kiu.the best tools money can buy
10.have testers
11.new joiner write code during their interview
12.do hallway[走廊-随机] usability testing
---------------------testing fits----------------------------------
@teisng level:1.the module level;2.bigger;4.much bigger;3.Integration
@check daily building;bug database;how you are doing against the schedule;
against the specification;usability testing checking what user want;
@less obvious issues:repeated means [automated];

-------------------------------------------------------- 3/22/2015 Sunday