2009년 2월 24일 화요일

IE 7 에서 E-load 7.X 설치방법

image

1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Version 값을 6.0으로 변경해준후 설치하면된다.

만약을 위해 백업을 해두시길..

댓글 없음:
라벨: ,

2009년 2월 19일 목요일

Top10 Negative Test Cases

Top 10 Negative Test Cases

Negative test cases are designed to test the software in ways it was not intended to be used, and should be a part of your testing effort.  Below are the top 10 negative test cases you should consider when designing your test effort:

  1. Embedded Single Quote - Most SQL based database systems have issues when users store information that contain a single quote (e.g. John's car).  For each screen that accepts alphanumeric data entry, try entering text that contains one or more single quotes.
  2. Required Data Entry - Your functional specification should clearly indicate fields that require data entry on screens.  Test each field on the screen that has been indicated as being required to ensure it forces you to enter data in the field.
  3. Field Type Test - Your functional specification should clearly indicate fields that require specific data entry requirements (date fields, numeric fields, phone numbers, zip codes, etc).  Test each field on the screen that has been indicated as having special types to ensure it forces you to enter data in the correct format based on the field type (numeric fields should not allow alphabetic or special characters, date fields should require a valid date, etc).
  4. Field Size Test - Your functional specification should clearly indicate the number of characters you can enter into a field (for example, the first name must be 50 or less characters).  Write test cases to ensure that you can only enter the specified number of characters. Preventing the user from entering more characters than is allowed is more elegant than giving an error message after they have already entered too many characters.
  5. Numeric Bounds Test - For numeric fields, it is important to test for lower and upper bounds. For example, if you are calculating interest charged to an account, you would never have a negative interest amount applied to an account that earns interest, therefore, you should try testing it with a negative number.   Likewise, if your functional specification requires that a field be in a specific range (e.g. from 10 to 50), you should try entering 9 or 51, it should fail with a graceful message.
  6. Numeric Limits Test - Most database systems and programming languages allow numeric items to be identified as integers or long integers.  Normally, an integer has a range of -32,767 to 32,767 and long integers can range from
    -2,147,483,648 to 2,147,483,647.  For numeric data entry that do not have specified bounds limits, work with these limits to ensure that it does not get an numeric overflow error.
  7. Date Bounds Test - For date fields, it is important to test for lower and upper bounds. For example, if you are checking a birth date field, it is probably a good bet that the person's birth date is no older than 150 years ago.  Likewise, their birth date should not be a date in the future.
  8. Date Validity - For date fields, it is important to ensure that invalid dates are not allowed (04/31/2007 is an invalid date).  Your test cases should also check for leap years (every 4th and 400th year is a leap year).
  9. Web Session Testing - Many web applications rely on the browser session to keep track of the person logged in, settings for the application, etc.  Most screens in a web application are not designed to be launched without first logging in.   Create test cases to launch web pages within the application without first logging in.  The web application should ensure it has a valid logged in session before rendering pages within the application.
  10. Performance Changes - As you release new versions of your product, you should have a set of performance tests that you run that identify the speed of your screens (screens that list information, screens that add/update/delete data, etc).   Your test suite should include test cases that compare the prior release performance statistics to the current release.  This can aid in identifying potential performance problems that will be manifested with code changes to the current release.


Helpful Templates

Below are some helpful templates to aid you in developing software solutions on-time and on-budget:

About the Author
Steve Miller is the President of Pragmatic Software (http://www.PragmaticSW.com).  With over 21 years of experience, Steve has extensive knowledge in project management, software architecture and test design. Steve publishes a monthly newsletter for companies that design and develop software.  You can read other newsletters at http://www.PragmaticSW.com/Newsletters.asp.  Steve's email is steve.miller@PragmaticSW.com.

Pragmatic Software Co., Inc.
383 Inverness Parkway
Suite 280
Englewood, CO 80112

Phone: 303.768.7480
Fax: 303.768.7481
Web site: http://www.PragmaticSW.com
E-mail: info@PragmaticSW.com

댓글 없음:

아파치 서버(소스 컴파일) 설치하기 실습

아파치 서버(소스 컴파일) 설치하기 실습
먼저 이미 설치되어 있는 Apache 버전이 있는지 확인해 본다.
Sun Microsystems Inc.  SunOS 5.9      Generic May 2002
bash-2.05# pkginfo | grep httpd
bash-2.05# pkginfo | grep apache
bash-2.05# ps -ef | grep httpd
    root  769  501  0 14:12:09 pts/6    0:00 grep httpd
    --패키지로 설치 됐다면 삭제함.
    pkgrm 명령어로 지움
--설치전 다음과 같은 패키지 설치
make    -- make 설치후 링크 걸기
bash-2.05#ln -s /usr/local/bin/make /usr/bin/make
-- 패키지 설치 
expat,
libiconv,
gdbm,
db-4.2.52.NC,
openssl-0.9.7g
libgcc
gcc
-- 패키지 설치 방법
bash-2.05# gunzip openssl-0.9.7g-sol9-sparc-local.gz
bash-2.05# pkgadd -d openssl-0.9.7g-sol9-sparc-local
-- 다음과 같이 모든 패키지를 설치한다.
--환경 변수(PATH) 를 다음과 같이 설정한다.
bash-2.05# cat /.bash_profile
export PS1='\u@\H:\w>'
export PATH=$PATH:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/local:/usr/local/lib:/usr/local/bin:/usr/local/doc
bash-2.05#
bash-2.05#source .bash_profile --환경변수 적용
먼저 아파치 최신판을 다운로드 받아보겠다. 아파치의 배포판은
http://apache.org 에서 다운로드 받아보겠다.
다음과 같이 최신 버전을 설치 httpd-2.0.54.tar.gz (소스 컴파일로 설치)
bash-2.05#gunzip httpd-2.0.54.tar.gz
bash-2.05#tar -xvf httpd-2.0.54.tar
bash-2.05# cd httpd-2.0.54
bash-2.05# ls
ABOUT_APACHE      LICENSE          VERSIONING        config.nice      include          srclib
Apache.dsp        Makefile          acconfig.h        config.status    libhttpd.dsp      support
Apache.dsw        Makefile.in      acinclude.m4      configure        modules          test
BuildBin.dsp      Makefile.win      apachenw.mcp.zip  configure.in      modules.c
CHANGES          NOTICE            build            docs              modules.lo
INSTALL          NWGNUmakefile    buildconf        emacs-style      modules.o
InstallBin.dsp    README            config.layout    httpd            os
LAYOUT            README.platforms  config.log        httpd.spec        server
bash-2.05#./configure --prefix=/usr/local/apache2 --enable-mods-shared=all
            --enable-ssl=shared --enable-ssl --with-ssl=/usr/local/ssl
--configure 구성옵션 참조하기
http://httpd.apache.org/docs/2.0/ko/programs/configure.html
bash-2.05#make
bash-2.05#make install
--make 와 make install 동시에 실행하기
--bash-2.05#make && make install
--한번에 성공하길 ....
--만약 make 실패 제거 명령어
--bash-2.05#make clean
bash-2.05# pwd
/usr/local/apache2/conf
bash-2.05# ls
highperformance-std.conf  httpd.conf                mime.types
highperformance.conf      httpd1.conf              ssl-std.conf
httpd-std.conf            magic                    ssl.conf
bash-2.05#
bash-2.05# pwd
/usr/local/apache2/conf
-------------------------------------
  아파치 설정
-------------------------------------
bash-2.05# vi httpd.conf
328  #ServerName www.example.com:80
329  ServerName 203.247.202.47:80
--라인 주석 처리후 서버 IP 나 도메인 주소 입력
--후 포트 넘버 웹서버 80 명시
50  ServerRoot "/usr/local/apache2"
370  <Directory "/usr/local/apache2/htdocs">
--주석 제거후 다음과 같이 설정
345  DocumentRoot "/usr/local/apache2/htdocs"
--홈페이지 문서 루트 위치 지정함
410  #<Directory /home/*/public_html>
411  #    AllowOverride FileInfo AuthConfig Limit Indexes
412  #    Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
413  #    <Limit GET POST OPTIONS PROPFIND>
414  #        Order allow,deny
415  #        Allow from all
416  #    </Limit>
417  #    <LimitExcept GET POST OPTIONS PROPFIND>
418  #        Order deny,allow
419  #        Deny from all
420  #    </LimitExcept>
421  #</Directory>
--다음과 같이 주석 제거함
410  <Directory /home/*/public_html>
411      AllowOverride FileInfo AuthConfig Limit Indexes
412      Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
413      <Limit GET POST OPTIONS PROPFIND>
414          Order allow,deny
415          Allow from all
416      </Limit>
417      <LimitExcept GET POST OPTIONS PROPFIND>
418          Order deny,allow
419          Deny from all
420      </LimitExcept>
421  </Directory>
:wq!
--아파치 설정 다음과 같이 수정합니다.
------------------------------------
bash-2.05#./apachectl start  --아파치 서버 가동
-- bash-2.05#./apachectl stop  --아파치 서버 중지
bash-2.05# ps -ef | grep httpd --아파치 프로세스 확인
    root  3037  535  0 15:57:33 pts/6    0:00 vi httpd.conf
    root  3097  528  0 18:51:05 pts/5    0:00 grep httpd
  nobody  2919  2912  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
  nobody  2920  2912  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
  nobody  2918  2912  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
  nobody  2917  2912  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
  nobody  2932  2912  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
  nobody  2916  2912  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
    root  2912    1  0  7월 25 ?        0:00 /usr/local/apache2/bin/httpd -k start
bash-2.05#
bash-2.05# cd htdocs/
bash-2.05# ls
index.html
bash-2.05# pwd
/usr/local/apache2/htdocs
--다음과 같이 문서 홈 루트(/usr/local/apache2/htdoc)에
--index.html 파일 생성
bash-2.05# cat index.html
<html>
<head><title>Apache Test</title></head>
<body>
Apache Song Dae Sung Wow!!!
</body>
</html>
bash-2.05#
--브라우저로 확인
--url://http://localhost
로 작동 여부 확인

댓글 없음:
라벨: ,
피드 구독하기: 글 (Atom)