|
1 | 1 | - 성능측정 : <http://www.codeplex.com/PerfTestingGuide> |
2 | | -- [Software QA Testing and Test Tool |
3 | | - Resources](http://www.aptest.com/resources.html#api) |
4 | | -- [How to break Software |
5 | | - PPT](http://www.math.uaa.alaska.edu/%7Eafkjm/cs470/handouts/breaking.pdf) |
6 | | -- [How to break Software Other |
7 | | - PPT](http://www.mrtc.mdh.se/rtis2003/pres/Keynote1Whittaker.pdf) |
| 2 | +- [Software QA Testing and Test Tool Resources](http://www.aptest.com/resources.html#api) |
| 3 | +- [How to break Software PPT](http://www.math.uaa.alaska.edu/%7Eafkjm/cs470/handouts/breaking.pdf) |
| 4 | +- [How to break Software Other PPT](http://www.mrtc.mdh.se/rtis2003/pres/Keynote1Whittaker.pdf) |
8 | 5 | - [침투테스트](http://msdn.microsoft.com/ko-kr/magazine/cc507646.aspx) |
9 | | -- [제임스 바흐의 쾌속 소프트웨어 테스팅 |
10 | | - 교육](http://agile.egloos.com/4599387) |
11 | | - |
12 | | -- [Testing |
13 | | - process](http://www.slideshare.net/Byungwook/testing-process?type=presentation) |
| 6 | +- [제임스 바흐의 쾌속 소프트웨어 테스팅 교육](http://agile.egloos.com/4599387) |
| 7 | +- [Testing process](http://www.slideshare.net/Byungwook/testing-process?type=presentation) |
14 | 8 |
|
15 | 9 | # 테스트 종류 |
16 | 10 |
|
17 | 11 | - [테스트의 종류](http://blog.naver.com/phrack/80051146924) (신상재님) |
18 | | -- [단위 테스팅과 통합, 승인, 기능 |
19 | | - 테스팅](https://justhackem.wordpress.com/2016/05/23/unit-integration-acceptance-and-functional-testing/) |
20 | | - (이규원님) |
| 12 | +- [단위 테스팅과 통합, 승인, 기능 테스팅](https://justhackem.wordpress.com/2016/05/23/unit-integration-acceptance-and-functional-testing/) (이규원님) |
21 | 13 |
|
22 | 14 | ## 논쟁 |
23 | | - |
24 | | -- [코드리뷰와 인스펙션이 테스트보다 효과적이고 블랙박스 테스트가 |
25 | | - 단위테스트/개발자테스트보다 낫다고?](http://toby.epril.com/?p=608) |
| 15 | +- [코드리뷰와 인스펙션이 테스트보다 효과적이고 블랙박스 테스트가 단위테스트/개발자테스트보다 낫다고?](http://toby.epril.com/?p=608) |
26 | 16 |
|
27 | 17 | ## 테스트업무 |
28 | | - |
29 | | -- [좋은 테스터가 되기 위한 |
30 | | - 요건](http://www.ibm.com/developerworks/kr/library/dwclm/20080115/?ca=dnn-krt-20080123) |
31 | | - |
32 | | -- [Developers, Don’t Write Functional |
33 | | - Tests!](http://blog.mgm-tp.com/2010/11/successful-software-testing-part1/) |
| 18 | +- [좋은 테스터가 되기 위한 요건](http://www.ibm.com/developerworks/kr/library/dwclm/20080115/?ca=dnn-krt-20080123) |
| 19 | +- [Developers, Don’t Write Functional Tests!](http://blog.mgm-tp.com/2010/11/successful-software-testing-part1/) |
34 | 20 |
|
35 | 21 | ## Bug Report |
36 | | - |
37 | 22 | - <http://www.devbistro.com/articles/Testing/How-to-Write-Effective-Bug-Reports> |
38 | 23 | - <http://www.softwaretestinghelp.com/how-to-write-good-bug-report/> |
39 | 24 |
|
40 | | -## GTAC |
41 | | - |
42 | 25 | ## Children |
43 | | -- [[junit]] |
44 | 26 | - [[mock]] |
45 | 27 | - [[performance-test]] |
46 | 28 | - [[tdd]] |
47 | 29 | - [[test-framework]] |
48 | 30 | - [[test-quote]] |
49 | 31 | - [[ui-test]] |
50 | | - |
51 | | -## Related |
52 | 32 | - [[code-coverage]] |
0 commit comments