Software testing

From Wikipedia, the free encyclopedia

Jump to: navigation, search

Software development process
Activities and steps
Requirements· Specification Architecture· Design Implementation· Testing Deployment· Maintenance
Models
Agile· Cleanroom· DSDM Iterative· RAD · RUP · Spiral Waterfall· XP· Scrum · Lean V-Model · FDD · TDD
Supporting disciplines
Configuration management Documentation Quality assurance (SQA) Project management User experience design
Tools
Compiler · Debugger · Profiler GUI designer Integrated development environment
v•d•e

Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.^[1] Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs.

Software Testing can also be stated as the process of validating and verifying that a software program/application/product:

1. meets the business and technical requirements that guided its design and development;
2. works as expected; and
3. can be implemented with the same characteristics.

Software Testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the Software Development methodology adopted.

Different software development models will focus the test effort at different points in the development process. Newer development models, such as Agile, often employ test driven development and place an increased portion of the testing in the hands of the developer, before it reaches a formal team of testers. In a more traditional model, most of the test execution occurs after the requirements have been defined and the coding process has been completed.

Contents [hide] 1 Overview 2 History 3 Software testing topics 3.1 Scope 3.2 Functional vs non-functional testing 3.3 Defects and failures 3.4 Finding faults early 3.5 Compatibility 3.6 Input combinations and preconditions 3.7 Static vs. dynamic testing 3.8 Software verification and validation 3.9 The software testing team 3.10 Software Quality Assurance (SQA) 4 Testing methods 4.1 The box approach 4.1.1 Black box testing 4.1.2 White box testing 4.1.3 Grey Box Testing 5 Testing Levels 5.1 Unit Testing 5.2 Integration Testing 5.3 System Testing 5.4 System Integration Testing 5.5 Regression Testing 5.6 Acceptance testing 5.7 Alpha testing 5.8 Beta testing 6 Non Functional Software Testing 6.1 Software performance testing and load testing 6.2 Stability testing 6.3 Usability testing 6.4 Security testing 6.5 Internationalization and localization 6.6 Destructive testing 7 The testing process 7.1 Traditional CMMI or waterfall development model 7.2 Agile or Extreme development model 7.3 A sample testing cycle 8 Automated testing 8.1 Testing Tools 8.2 Measurement in software testing 9 Testing artifacts 10 Certifications 11 Controversy 12 See also 13 References 14 External links

[edit] Overview

Testing can never completely identify all the defects within software. Instead, it furnishes a criticism or comparison that compares the state and behavior of the product against oracles—principles or mechanisms by which someone might recognize a problem. These oracles may include (but are not limited to) specifications, contracts,^[2] comparable products, past versions of the same product, inferences about intended or expected purpose, user or customer expectations, relevant standards, applicable laws, or other criteria.

Every software product has a target audience. For example, the audience for video game software is completely different from banking software. Therefore, when an organization develops or otherwise invests in a software product, it can assess whether the software product will be acceptable to its end users, its target audience, its purchasers, and other stakeholders. Software testing is the process of attempting to make this assessment.

A study conducted by NIST in 2002 reports that software bugs cost the U.S. economy $59.5 billion annually. More than a third of this cost could be avoided if better software testing was performed.^[3]

[edit] History

The separation of debugging from testing was initially introduced by Glenford J. Myers in 1979.^[4] Although his attention was on breakage testing ("a successful test is one that finds a bug"^[4][5]) it illustrated the desire of the software engineering community to separate fundamental development activities, such as debugging, from that of verification. Dave Gelperin and William C. Hetzel classified in 1988 the phases and goals in software testing in the following stages:^[6]

• Until 1956 - Debugging oriented^[7]
• 1957–1978 - Demonstration oriented^[8]
• 1979–1982 - Destruction oriented^[9]
• 1983–1987 - Evaluation oriented^[10]
• 1988–2000 - Prevention oriented^[11]

[edit] Software testing topics

[edit] Scope

A primary purpose for testing is to detect software failures so that defects may be uncovered and corrected. This is a non-trivial pursuit. Testing cannot establish that a product functions properly under all conditions but can only establish that it does not function properly under specific conditions.^[12] The scope of software testing often includes examination of code as well as execution of that code in various environments and conditions as well as examining the aspects of code: does it do what it is supposed to do and do what it needs to do. In the current culture of software development, a testing organization may be separate from the development team. There are various roles for testing team members. Information derived from software testing may be used to correct the process by which software is developed.^[13]

[edit] Functional vs non-functional testing

Functional testing refers to tests that verify a specific action or function of the code. These are usually found in the code requirements d0cumentation, although some development methodologies work from use cases or user stories. Functional tests tend to answer the question of "can the user do this" or "does this particular feature work".

Non-functional testing refers to aspects of the software that may not be related to a specific function or user action, such as scalability or security. Non-functional testing tends to answer such questions as "how many people can log in at once", or "how easy is it to hack this software".

[edit] Defects and failures

Not all software defects are caused by coding errors. One common source of expensive defects is caused by requirement gaps, e.g., unrecognized requirements, that result in errors of omission by the program designer.^[14] A common source of requirements gaps is non-functional requirements such as testability, scalability, maintainability, usability, performance, and security.

Software faults occur through the following processes. A programmer makes an error (mistake), which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure.^[15] Not all defects will necessarily result in failures. For example, defects in dead code will never result in failures. A defect can turn into a failure when the environment is changed. Examples of these changes in environment include the software being run on a new hardware platform, alterations in source data or interacting with different software.^[15] A single defect may result in a wide range of failure symptoms.

[edit] Finding faults early

It is commonly believed that the earlier a defect is found the cheaper it is to fix it.^[16] The following table shows the cost of fixing the defect depending on the stage it was found.^[17] For example, if a problem in the requirements is found only post-release, then it would cost 10–100 times more to fix than if it had already been found by the requirements review.

		Time Detected
		Requirements	Architecture	Construction	System Test	Post-Release
Time Introduced	Requirements	1×	3×	5–10×	10×	10–100×
	Architecture	-	1×	10×	15×	25–100×
	Construction	-	-	1×	10×	10–25×

[edit] Compatibility

A common cause of software failure (real or perceived) is a lack of compatibility with other application software, operating systems (or operating system versions, old or new), or target environments that differ greatly from the original (such as a terminal or GUI application intended to be run on the desktop now being required to become a Web application, which must render in a Web browser). For example, in the case of a lack of backward compatibility, this can occur because the programmers develop and test software only on the latest version of the target environment, which not all users may be running. This results in the unintended consequence that the latest work may not function on earlier versions of the target environment, or on older hardware that earlier versions of the target environment was capable of using. Sometimes such issues can be fixed by proactively abstracting operating system functionality into a separate program module or library.

[edit] Input combinations and preconditions

A very fundamental problem with software testing is that testing under all combinations of inputs and preconditions (initial state) is not feasible, even with a simple product.^[12][18] This means that the number of defects in a software product can be very large and defects that occur infrequently are difficult to find in testing. More significantly, non-functional dimensions of quality (how it is supposed to be versus what it is supposed to do)—usability, scalability, performance, compatibility, reliability—can be highly subjective; something that constitutes sufficient value to one person may be intolerable to another.

[edit] Static vs. dynamic testing

There are many approaches to software testing. Reviews, walkthroughs, or inspections are considered as static testing, whereas actually executing programmed code with a given set of test cases is referred to as dynamic testing. Static testing can be (and unfortunately in practice often is) omitted. Dynamic testing takes place when the program itself is used for the first time (which is generally considered the beginning of the testing stage). Dynamic testing may begin before the program is 100% complete in order to test particular sections of code (modules or discrete functions). Typical techniques for this are either using stubs/drivers or execution from a debugger environment. For example, Spreadsheet programs are, by their very nature, tested to a large extent interactively ("on the fly"), with results displayed immediately after each calculation or text manipulation.

[edit] Software verification and validation

Software testing is used in association with verification and validation:^[19]

• Verification: Have we built the software right? (i.e., does it match the specification).
• Validation: Have we built the right software? (i.e., is this what the customer wants).

The terms verification and validation are commonly used interchangeably in the industry; it is also common to see these two terms incorrectly defined. According to the IEEE Standard Glossary of Software Engineering Terminology:

Verification is the process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase.

Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements.

[edit] The software testing team

Software testing can be done by software testers. Until the 1980s the term "software tester" was used generally, but later it was also seen as a separate profession. Regarding the periods and the different goals in software testing,^[20] different roles have been established: manager, test lead, test designer, tester, automation developer, and test administrator.

[edit] Software Quality Assurance (SQA)

Though controversial, software testing may be viewed as an important part of the software quality assurance (SQA) process.^[12] In SQA, software process specialists and auditors take a broader view on software and its development. They examine and change the software engineering process itself to reduce the amount of faults that end up in the delivered software: the so-called defect rate.

What constitutes an "acceptable defect rate" depends on the nature of the software. For example, an arcade video game designed to simulate flying an airplane would presumably have a much higher tolerance for defects than mission critical software such as that used to control the functions of an airliner that really is flying!

Although there are close links with SQA, testing departments often exist independently, and there may be no SQA function in some companies.

Software Testing is a task intended to detect defects in software by contrasting a computer program's expected results with its actual results for a given set of inputs. By contrast, QA (Quality Assurance) is the implementation of policies and procedures intended to prevent defects from occurring in the first place.

[edit] Testing methods

[edit] The box approach

Software testing methods are traditionally divided into black box testing and white box testing. These two approaches are used to describe the point of view that a test engineer takes when designing test cases.

[edit] Black box testing

Black box testing treats the software as a "black box"—without any knowledge of internal implementation. Black box testing methods include: equivalence partitioning, boundary value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix, exploratory testing and specification-based testing.

Specification-based testing: Specification-based testing aims to test the functionality of software according to the applicable requirements.^[21] Thus, the tester inputs data into, and only sees the output from, the test object. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either "is" or "is not" the same as the expected value specified in the test case.

Specification-based testing is necessary, but it is insufficient to guard against certain risks.^[22]

Advantages and disadvantages: The black box tester has no "bonds" with the code, and a tester's perception is very simple: a code must have bugs. Using the principle, "Ask and you shall receive," black box testers find bugs where programmers do not. But, on the other hand, black box testing has been said to be "like a walk in a dark labyrinth without a flashlight," because the tester doesn't know how the software being tested was actually constructed. As a result, there are situations when (1) a tester writes many test cases to check something that could have been tested by only one test case, and/or (2) some parts of the back-end are not tested at all.

Therefore, black box testing has the advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of "blind exploring," on the other. ^[23]

[edit] White box testing

White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these.

Types of white box testing

The following types of white box testing exist:

• API testing (application programming interface) - Testing of the application using Public and Private APIs
• Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once)
• Fault injection methods - improving the coverage of a test by introducing faults to test code paths
• Mutation testing methods
• Static testing - White box testing includes all static testing

Test coverage

White box testing methods can also be used to evaluate the completeness of a test suite that was created with black box testing methods. This allows the software team to examine parts of a system that are rarely tested and ensures that the most important function points have been tested.^[24]

Two common forms of code coverage are:

• Function coverage, which reports on functions executed
• Statement coverage, which reports on the number of lines executed to complete the test

They both return a code coverage metric, measured as a percentage.

[edit] Grey Box Testing

Grey box testing (American spelling: Gray box testing) involves having access to internal data structures and algorithms for purposes of designing the test cases, but testing at the user, or black-box level. Manipulating input data and formatting output do not qualify as grey box, because the input and output are clearly outside of the "black-box" that we are calling the system under test. This distinction is particularly important when conducting integration testing between two modules of code written by two different developers, where only the interfaces are exposed for test. However, modifying a data repository does qualify as grey box, as the user would not normally be able to change the data outside of the system under test. Grey box testing may also include reverse engineering to determine, for instance, boundary values or error messages.

[edit] Testing Levels

Tests are frequently grouped by where they are added in the software development process, or by the level of specificity of the test.

[edit] Unit Testing

Main article: Unit testing

Unit testing refers to tests that verify the functionality of a specific section of code, usually at the function level. In an object-oriented environment, this is usually at the class level, and the minimal unit tests include the constructors and destructors.^[25]

These type of tests are usually written by developers as they work on code (white-box style), to ensure that the specific function is working as expected. One function might have multiple tests, to catch corner cases or other branches in the code. Unit testing alone cannot verify the functionality of a piece of software, but rather is used to assure that the building blocks the software uses work independently of each other.

Unit testing is also called Component Testing.

[edit] Integration Testing

Main article: Integration testing

Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together ("big bang"). Normally the former is considered a better practice since it allows interface issues to be localised more quickly and fixed.

Integration testing works to expose defects in the interfaces and interaction between integrated components (modules). Progressively larger groups of tested software components corresponding to elements of the architectural design are integrated and tested until the software works as a system.^[26]

[edit] System Testing

Main article: System testing

System testing tests a completely integrated system to verify that it meets its requirements.^[27]

[edit] System Integration Testing

Main article: System integration testing

System integration testing verifies that a system is integrated to any external or third party systems defined in the system requirements.^{[citation needed]}

[edit] Regression Testing

Main article: Regression testing

Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, or old bugs that have come back. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the risk of the added features. They can either be complete, for changes added late in the release or deemed to be risky, to very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk.

[edit] Acceptance testing

Main article: Acceptance testing

Acceptance testing can mean one of two things:

1. A smoke test is used as an acceptance test prior to introducing a new build to the main testing process, i.e. before integration or regression.
2. Acceptance testing performed by the customer, often in their lab environment on their own HW, is known as user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off process between any two phases of development.^{[citation needed]}

[edit] Alpha testing

Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.^{[citation needed]}

[edit] Beta testing

Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users.^{[citation needed]}

[edit] Non Functional Software Testing

Special methods exist to test non-functional aspects of software. In contrast to functional testing, which establishes the correct operation of the software (correct in that it matches the expected behavior defined in the design requirements), non-functional testing verifies that the software functions properly even when it receives invalid or unexpected inputs. Software fault injection, in the form of fuzzing, is an example of non-functional testing. Non-functional testing, especially for software, is designed to establish whether the device under test can tolerate invalid or unexpected inputs, thereby establishing the robustness of input validation routines as well as error-handling routines. Various commercial non-functional testing tools are linked from the Software fault injection page; there are also numerous open-source and free software tools available that perform non-functional testing.

[edit] Software performance testing and load testing

Performance testing is executed to determine how fast a system or sub-system performs under a particular workload. It can also serve to validate and verify other quality attributes of the system, such as scalability, reliability and resource usage. Load testing is primarily concerned with testing that can continue to operate under a specific load, whether that be large quantities of data or a large number of users. This is generally referred to as software scalability. The related load testing activity of when performed as a non-functional activity is often referred to as Endurance Testing.

Volume testing is a way to test functionality. Stress testing is a way to test reliability. Load testing is a way to test performance. There is little agreement on what the specific goals of load testing are. The terms load testing, performance testing, reliability testing, and volume testing, are often used interchangeably.

[edit] Stability testing

Stability testing checks to see if the software can continuously function well in or above an acceptable period. This activity of Non Functional Software Testing is oftentimes referred to as load (or endurance) testing.

[edit] Usability testing

Usability testing is needed to check if the user interface is easy to use and understand.

[edit] Security testing

Security testing is essential for software that processes confidential data to prevent system intrusion by hackers.

[edit] Internationalization and localization

Internationalization and localization is needed to test these aspects of software, for which a pseudolocalization method can be used. It will verify that the application still works, even after it has been translated into a new language or adapted for a new culture (such as different currencies or time zones).

[edit] Destructive testing

Main article: Destructive testing

Destructive testing attempts to cause the software or a sub-system to fail, in order to test its robustness.

[edit] The testing process

[edit] Traditional CMMI or waterfall development model

A common practice of software testing is that testing is performed by an independent group of testers after the functionality is developed, before it is shipped to the customer.^[28] This practice often results in the testing phase being used as a project buffer to compensate for project delays, thereby compromising the time devoted to testing.^[29]

Another practice is to start software testing at the same moment the project starts and it is a continuous process until the project finishes.^[30]

[edit] Agile or Extreme development model

In counterpoint, some emerging software disciplines such as extreme programming and the agile software development movement, adhere to a "test-driven software development" model. In this process, unit tests are written first, by the software engineers (often with pair programming in the extreme programming methodology). Of course these tests fail initially; as they are expected to. Then as code is written it passes incrementally larger portions of the test suites. The test suites are continuously updated as new failure conditions and corner cases are discovered, and they are integrated with any regression tests that are developed. Unit tests are maintained along with the rest of the software source code and generally integrated into the build process (with inherently interactive tests being relegated to a partially manual build acceptance process). The ultimate goal of this test process is to achieve continuous deployment where software updates can be published to the public frequently. ^{[31] [32]}

[edit] A sample testing cycle

Although variations exist between organizations, there is a typical cycle for testing^[33]. The sample below is common among organizations employing the Waterfall development model.

• Requirements analysis: Testing should begin in the requirements phase of the software development life cycle. During the design phase, testers work with developers in determining what aspects of a design are testable and with what parameters those tests work.
• Test planning: Test strategy, test plan, testbed creation. Since many activities will be carried out during testing, a plan is needed.
• Test development: Test procedures, test scenarios, test cases, test datasets, test scripts to use in testing software.
• Test execution: Testers execute the software based on the plans and test d0cuments then report any errors found to the development team.
• Test reporting: Once testing is completed, testers generate metrics and make final reports on their test effort and whether or not the software tested is ready for release.
• Test result analysis: Or Defect Analysis, is done by the development team usually along with the client, in order to decide what defects should be treated, fixed, rejected (i.e. found software working properly) or deferred to be dealt with later.
• Defect Retesting: Once a defect has been dealt with by the development team, it is retested by the testing team. AKA Resolution testing.
• Regression testing: It is common to have a small test program built of a subset of tests, for each integration of new, modified, or fixed software, in order to ensure that the latest delivery has not ruined anything, and that the software product as a whole is still working correctly.
• Test Closure: Once the test meets the exit criteria, the activities such as capturing the key outputs, lessons learned, results, logs, d0cuments related to the project are archived and used as a reference for future projects.

[edit] Automated testing

Main article: Test automation

Many programming groups are relying more and more on automated testing, especially groups that use Test-driven development. There are many frameworks to write tests in, and Continuous Integration software will run tests automatically every time code is checked into a version control system.

While automation cannot reproduce everything that a human can do (and all the strange ways they think of doing it), it can be very useful for regression testing. However, it does require a well-developed test suite of testing scripts in order to be truly useful.

[edit] Testing Tools

Program testing and fault detection can be aided significantly by testing tools and debuggers. Testing/debug tools include features such as:

• Program monitors, permitting full or partial monitoring of program code including:
  • Instruction Set Simulator, permitting complete instruction level monitoring and trace facilities
  • Program animation, permitting step-by-step execution and conditional breakpoint at source level or in machine code
  • Code coverage reports
• Formatted dump or Symbolic debugging, tools allowing inspection of program variables on error or at chosen points
• Automated functional GUI testing tools are used to repeat system-level tests through the GUI
• Benchmarks, allowing run-time performance comparisons to be made
• Performance analysis (or profiling tools) that can help to highlight hot spots and resource usage

Some of these features may be incorporated into an Integrated Development Environment (IDE).

[edit] Measurement in software testing

Usually, quality is constrained to such topics as correctness, completeness, security,^{[citation needed]} but can also include more technical requirements as described under the ISO standard ISO 9126, such as capability, reliability, efficiency, portability, maintainability, compatibility, and usability.

There are a number of frequently-used software measures, often called "metrics", which are used to assist in determining the state of the software or the adequacy of the testing.

[edit] Testing artifacts

Software testing process can produce several artifacts.

Test plan

A test specification is called a test plan. The developers are well aware what test plans will be executed and this information is made available to management and the developers. The idea is to make them more cautious when developing their code or making additional changes. Some companies have a higher-level d0cument called a test strategy.

Traceability matrix

A traceability matrix is a table that correlates requirements or design d0cuments to test d0cuments. It is used to change tests when the source d0cuments are changed, or to verify that the test results are correct.

Test case

A test case normally consists of a unique identifier, requirement references from a design specification, preconditions, events, a series of steps (also known as actions) to follow, input, output, expected result, and actual result. Clinically defined a test case is an input and an expected result.^[34] This can be as pragmatic as 'for condition x your derived result is y', whereas other test cases described in more detail the input scenario and what results might be expected. It can occasionally be a series of steps (but often steps are contained in a separate test procedure that can be exercised against multiple test cases, as a matter of economy) but with one expected result or expected outcome. The optional fields are a test case ID, test step, or order of execution number, related requirement(s), depth, test category, author, and check boxes for whether the test is automatable and has been automated. Larger test cases may also contain prerequisite states or steps, and descriptions. A test case should also contain a place for the actual result. These steps can be stored in a word processor d0cument, spreadsheet, database, or other common repository. In a database system, you may also be able to see past test results, who generated the results, and what system configuration was used to generate those results. These past results would usually be stored in a separate table.

Test script

The test script is the combination of a test case, test procedure, and test data. Initially the term was derived from the product of work created by automated regression test tools. Today, test scripts can be manual, automated, or a combination of both.

Test suite

The most common term for a collection of test cases is a test suite. The test suite often also contains more detailed instructions or goals for each collection of test cases. It definitely contains a section where the tester identifies the system configuration used during testing. A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests.

Test data

In most cases, multiple sets of values or data are used to test the same functionality of a particular feature. All the test values and changeable environmental components are collected in separate files and stored as test data. It is also useful to provide this data to the client and with the product or a project.

Test harness

The software, tools, samples of data input and output, and configurations are all referred to collectively as a test harness.

[edit] Certifications

Several certification programs exist to support the professional aspirations of software testers and quality assurance specialists. No certification currently offered actually requires the applicant to demonstrate the ability to test software. No certification is based on a widely accepted body of knowledge. This has led some to declare that the testing field is not ready for certification.^[35] Certification itself cannot measure an individual's productivity, their skill, or practical knowledge, and cannot guarantee their competence, or professionalism as a tester.^[36]

Software testing certification types

• Exam-based: Formalized exams, which need to be passed; can also be learned by self-study [e.g., for ISTQB or QAI]^[37]
• Education-based: Instructor-led sessions, where each course has to be passed [e.g., International Institute for Software Testing (IIST)].

Testing certifications

• Certified Associate in Software Testing (CAST) offered by the Quality Assurance Institute (QAI)^[38]
• CATe offered by the International Institute for Software Testing^[39]
• Certified Manager in Software Testing (CMST) offered by the Quality Assurance Institute (QAI)^[38]
• Certified Software Tester (CSTE) offered by the Quality Assurance Institute (QAI)^[38]
• Certified Software Test Professional (CSTP) offered by the International Institute for Software Testing^[39]
• CSTP (TM) (Australian Version) offered by K. J. Ross & Associates^[40]
• ISEB offered by the Information Systems Examinations Board
• ISTQB Certified Tester, Foundation Level (CTFL) offered by the International Software Testing Qualification Board ^[41][42]
• ISTQB Certified Tester, Advanced Level (CTAL) offered by the International Software Testing Qualification Board ^[41][42]
• TMPF TMap^{[dubious – discuss]} Next Foundation offered by the Examination Institute for Information Science^[43]

Quality assurance certifications

• CMSQ offered by the Quality Assurance Institute (QAI)^[38].
• CSQA offered by the Quality Assurance Institute (QAI)^[38]
• CSQE offered by the American Society for Quality (ASQ)^[44]
• CQIA offered by the American Society for Quality (ASQ)^[44]

[edit] Controversy

Some of the major software testing controversies include:

What constitutes responsible software testing?

Members of the "context-driven" school of testing^[45] believe that there are no "best practices" of testing, but rather that testing is a set of skills that allow the tester to select or invent testing practices to suit each unique situation.^[46]

Agile vs. traditional

Should testers learn to work under conditions of uncertainty and constant change or should they aim at process "maturity"? The agile testing movement has received growing popularity since 2006 mainly in commercial circles ^[47][48], whereas government and military^[49] software providers are slow to embrace this methodology^{[neutrality is disputed]} in favour of traditional test-last models (e.g. in the Waterfall model).

Exploratory test vs. scripted^[50]

Should tests be designed at the same time as they are executed or should they be designed beforehand?

Manual testing vs. automated

Some writers believe that test automation is so expensive relative to its value that it should be used sparingly.^[51] More in particular, test-driven development states that developers should write unit-tests of the XUnit type before coding the functionality. The tests then can be considered as a way to capture and implement the requirements.

Software design vs. software implementation^[52]

Should testing be carried out only at the end or throughout the whole process?

Who watches the watchmen?

The idea is that any form of observation is also an interaction—the act of testing can also affect that which is being tested^[53].

[edit] See also

Software Testing portal

	Book:Software testing
Books are collections of articles which can be downloaded or ordered in print.

• All-pairs testing
• Automated testing
• Dynamic program analysis
• Formal verification
• GUI software testing
• Manual testing
• Orthogonal array testing
• Pair Testing
• Reverse semantic traceability
• Software testability
• Static code analysis
• Time Partition Testing (TPT)
• Web testing

[edit] References

1. ^ http://www.kaner.com/pdfs/ETatQAI.pdf Exploratory Testing], Cem Kaner, Florida Institute of Technology, Quality Assurance Institute Worldwide Annual Software Testing Conference, Orlando, FL, November 2006
2. ^ Leitner, A., Ciupa, I., Oriol, M., Meyer, B., Fiva, A., "Contract Driven Development = Test Driven Development - Writing Test Cases", Proceedings of ESEC/FSE'07: European Software Engineering Conference and the ACM SIGSOFT Symposium on the Foundations of Software Engineering 2007, (Dubrovnik, Croatia), September 2007
3. ^ Software errors cost U.S. economy $59.5 billion annually, NIST report
4. ^ ^{a b} Myers, Glenford J. (1979). The Art of Software Testing. John Wiley and Sons. ISBN0-471-04328-1.
5. ^ Dr. Dobb's journal of software tools for the professional programmer (M&T Pub) 12 (1-6): 116. 1987. http://books.google.com/books?id=7RoIAAAAIAAJ&q="a+successful+test+is+one+that+finds+a+bug&dq="a+successful+test+is+one+that+finds+a+bug&ei=U44OSsOxBpKSzgSxo4mXAg&pgis=1.
6. ^ Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.
7. ^ until 1956 it was the debugging oriented period, when testing was often associated to debugging: there was no clear difference between testing and debugging. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.
8. ^ From 1957–1978 there was the demonstration oriented period where debugging and testing was distinguished now - in this period it was shown, that software satisfies the requirements. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.
9. ^ The time between 1979–1982 is announced as the destruction oriented period, where the goal was to find errors. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.
10. ^ 1983–1987 is classified as the evaluation oriented period: intention here is that during the software lifecycle a product evaluation is provided and measuring quality. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.
11. ^ From 1988 on it was seen as prevention oriented period where tests were to demonstrate that software satisfies its specification, to detect faults and to prevent faults. Gelperin, D.; B. Hetzel (1988). "The Growth of Software Testing". CACM 31 (6). ISSN 0001-0782.
12. ^ ^{a b c} Kaner, Cem; Falk, Jack and Nguyen, Hung Quoc (1999). Testing Computer Software, 2nd Ed.. New York, et al: John Wiley and Sons, Inc.. pp.480 pages. ISBN0-471-35846-0.
13. ^ Kolawa, Adam; Huizinga, Dorota (2007). Automated Defect Prevention: Best Practices in Software Management. Wiley-IEEE Computer Society Press. p.41–43. ISBN0470042125. http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html.
14. ^ Kolawa, Adam; Huizinga, Dorota (2007). Automated Defect Prevention: Best Practices in Software Management. Wiley-IEEE Computer Society Press. p.86. ISBN0470042125. http://www.wiley.com/WileyCDA/WileyTitle/productCd-0470042125.html.
15. ^ ^{a b} Section 1.1.2, Certified Tester Foundation Level Syllabus, International Software Testing Qualifications Board
16. ^ Kaner, Cem; James Bach, Bret Pettichord (2001). Lessons Learned in Software Testing: A Context-Driven Approach. Wiley. p.4. ISBN0-471-08112-4.
17. ^ McConnell, Steve (2004). Code Complete (2nd ed.). Microsoft Press. pp.960. ISBN0-7356-1967-0.
18. ^ Principle 2, Section 1.3, Certified Tester Foundation Level Syllabus, International Software Testing Qualifications Board
19. ^ Tran, Eushiuan (1999). "Verification/Validation/Certification". in Koopman, P.. Topics in Dependable Embedded Systems. USA: Carnegie Mellon University. http://www.ece.cmu.edu/~koopman/des_s99/verification/index.html. Retrieved 2008-01-13.
20. ^ see D. Gelperin and W.C. Hetzel
21. ^ Laycock, G. T. (1993) (PostScript). The Theory and Practice of Specification Based Software Testing. Dept of Computer Science, Sheffield University, UK. http://www.mcs.le.ac.uk/people/gtl1/thesis.ps.gz. Retrieved 2008-02-13.
22. ^ Bach, James (June 1999). "Risk and Requirements-Based Testing" (PDF). Computer 32 (6): 113–114. http://www.satisfice.com/articles/requirements_based_testing.pdf. Retrieved 2008-08-19.
23. ^ Savenkov, Roman (2008). How to Become a Software Tester. Roman Savenkov Consulting. p.168. ISBN978-0-615-23372-7.
24. ^ Introduction, Code Coverage Analysis, Steve Cornett
25. ^ Binder, Robert V. (1999). Testing Object-Oriented Systems: Objects, Patterns, and Tools. Addison-Wesley Professional. p.45. ISBN0-201-80938-9.
26. ^ Beizer, Boris (1990). Software Testing Techniques (Second ed.). New York: Van Nostrand Reinhold. pp.21,430. ISBN0-442-20672-0.
27. ^ IEEE (1990). IEEE Standard Computer Dictionary: A Compilation of IEEE Standard Computer Glossaries. New York: IEEE. ISBN1559370793.
28. ^ e)Testing Phase in Software Testing:-
29. ^ Myers, Glenford J. (1979). The Art of Software Testing. John Wiley and Sons. p.145–146. ISBN0-471-04328-1.
30. ^ Dustin, Elfriede (2002). Effective Software Testing. Addison Wesley. p.3. ISBN0-20179-429-2.
31. ^ Marchenko, Artem (November 16, 2007). "XP Practice: Continuous Integration". http://agilesoftwaredevelopment.com/xp/practices/continuous-integration. Retrieved 2009-11-16.
32. ^ Gurses, Levent (February 19, 2007). "Agile 101: What is Continuous Integration?". http://www.jacoozi.com/blog/?p=18. Retrieved 2009-11-16.
33. ^ Pan, Jiantao (Spring 1999). "Software Testing (18-849b Dependable Embedded Systems)". Topics in Dependable Embedded Systems. Electrical and Computer Engineering Department, Carnegie Mellon University. http://www.ece.cmu.edu/~koopman/des_s99/sw_testing/.
34. ^ IEEE (1998). IEEE standard for software test d0cumentation. New York: IEEE. ISBN0-7381-1443-X.
35. ^ Kaner, Cem (2001). "NSF grant proposal to "lay a foundation for significant improvements in the quality of academic and commercial courses in software testing"" (pdf). http://www.testingeducation.org/general/nsf_grant.pdf.
36. ^ Kaner, Cem (2003). "Measuring the Effectiveness of Software Testers" (pdf). http://www.testingeducation.org/a/mest.pdf.
37. ^ Black, Rex (December 2008). Advanced Software Testing- Vol. 2: Guide to the ISTQB Advanced Certification as an Advanced Test Manager. Santa Barbara: Rocky Nook Publisher. ISBN1933952369.
38. ^ ^{a b c d e} Quality Assurance Institute
39. ^ ^{a b} International Institute for Software Testing
40. ^ K. J. Ross & Associates
41. ^ ^{a b} "ISTQB". http://www.istqb.org/.
42. ^ ^{a b} "ISTQB in the U.S.". http://www.astqb.org/.
43. ^ EXIN: Examination Institute for Information Science
44. ^ ^{a b} American Society for Quality
45. ^ context-driven-testing.com
46. ^ Article on taking agile traits without the agile method.
47. ^ “We’re all part of the story” by David Strom, July 1, 2009
48. ^ IEEE article about differences in adoption of agile trends between experienced managers vs. young students of the Project Management Institute. See also Agile adoption study from 2007
49. ^ Agile software development practices slowly entering the military
50. ^ IEEE article on Exploratory vs. Non Exploratory testing
51. ^ An example is Mark Fewster, Dorothy Graham: Software Test Automation. Addison Wesley, 1999, ISBN 0-201-33140-3.
52. ^ Article referring to other links questioning the necessity of unit testing
53. ^ Microsoft Development Network Discussion on exactly this topic

1. 정보시스템 감리사 시험은 언제 시행하나요?
○년 1회 실시
○2008년의 경우 7월 12일(토)에 실시
*시험주관 기관은 정보사회진흥원이 정통부 산하 기관에서 행안부 산하기관으로 변경이 되었고, 현재 정부 공공기관 통폐합 대상 기관에포함되어 있기 때문에 7월보다 더 늦어질 가능성이 있지만, 7월을 목표로 준비하시면 될 것 같습니다

2. 응시자격은?
① 기술사
② 기사자격을 가진 자로서 정보처리분야의 실무경력 7년 이상인 자
③ 산업기사자격을 가진 자로서 정보처리분야의 실무경력 10년 이상인 자
④ 박사학위를 가진 자(정보처리분야 학위소지자)
⑤ 석사학위를 가진 자로서 정보처리분야의 실무경력 6년 이상인 자
⑥ 학사학위를 가진 자로서 정보처리분야의 실무경력 9년 이상인 자
⑦ 전문대학을 졸업한 자로서 정보처리분야의 실무경력 12년 이상인 자
⑧ 고등학교를 졸업한 자로서 정보처리분야의 실무경력 15년 이상인 자
※ 기술사 자격명 : 정보관리, 전자계산조직응용, 정보통신 기술사
※ 기사 자격명 : 정보처리, 전자계산기조직응용, 정보통신 기사
※ 산업기사 자격명 : 정보처리, 정보기술, 전자계산기조직응용, 사무자동화 (컴퓨터 활용능력 자격은 해당 없음), 정보통신 산업기사
※ 경력은 자격 또는 학위 취득 후부터 산정함.

3. 정보시스템 감리사 시험 과목, 문항 수, 시험시간은?
○시험과목 : 감리 및 사업관리(25문), 소프트웨어 공학(25문), 데이터베이스(25문), 시스템 구조 및 보안(25문)
○문제유형 : 객관식
○문항 수 : 100문제
○시험시간 : 100분
* 문항수가 증가한다든가, 주관식 문제가 출제된다든가 하는 시행 규칙변경에 대해서는 항상 이야기가 나오지만 일단 위 기준으로 준비하시면 됩니다.
실제 시험 방법이나 과목이 변경이 된다면 시험 일자는 연기가 될 것 입니다.
* 마지막 과목은 시스템 구조 및 보안 문제만 나오지 않습니다. 경영기반, 네트워크 등의 문제도 출제되고 있습니다.
* 시험시간은 부족한 편입니다. 특히 OMR카드에 기표를 해야 하는 만큼 실제 시헙 시간은 90분으로 생각하시고 준비하시면 됩니다.

4. 합격기준은?
○합격자 인원 : 40명
○필기전형 과목별 40점 이상자 중 총점결과 순으로 상위 40명 선정
- 필기시험 후, 총점결과 40위 이내인 자와 예비합격자 등 필기시험 합격예정자는 자격을 증빙할 수 있는 증빙서류(경력증명서, 최종학력 증명서, 자격증 사본)를 제출함.
※ 증빙서류 검토결과 불합격자 발생에 대비하여 일정 범위의 예비합격자를 포함하여 필기시험 합격예정자를 공지함.
- 제출된 증빙서류 심사 후, 필기시험 최종합격자 40명을 선정함.
○필기전형 총점의 동일 점수 취득자가 다수인 경우 아래 순으로 순위 부여
- 감리 및 사업관리 과목 우수자→ 소프트웨어공학 과목 우수자 → 데이터베이스 과목 우수자 → 시스템 구조 및 보안 과목 우수자 → 생년월일 연소자
(위 기준은 2008년 기준이기 때문에 2009년의 경우 변경될 수 있습니다)

5. 문제의 난이도는?
○결론부터 말씀 드리면 많이 어렵고, 회가 거듭될 수록 난이도가 높아지고 있습니다.
객관식이니까 예상문제 몇 개 풀어보고 시험 보면 되겠지라고 생각하시면 안됩니다.
문제의 지문이 길어지는 추세며, 계산문제도 많습니다. 특히 데이타베이스 문제는 응용문제들이 출제되고 있기 때문에 더욱더 기본 지식이 충실해야 합니다
○아래에는 역대 응시자 수와 합격 커트라인에 대해서 알고 있는데로 정리를 했습니다.
----------------------------------------
년도 접수자 합격자 합격율 커드라인
----------------------------------------
2004년 277명 40명 14.4% 65점
2005년 323명 40명 12.4% 66점
2006년 615명 80명 13% 68점
2007년 821명 80명 9.7% 71점
2008년 917명 40명 4.3% 69점
(2006~2007년만 한시적으로 80명을 뽑았습니다)
* 상기 자료의 경쟁율은 사실 무의미 합니다. 실질적으로 합격 가능권에 계신분들은 (소위 말하는 일진) 아주 넓게 잡아서150-200명입니다. 나머지 분들은 그냥 시험을 보시는 분들입니다. 따라서 내가 일진에 들어갈 수 있는 수준인지에 대해서지속적인 체크가 필요한데 이것은 학원의 모의 고사를 통해서 가능합니다. 일반적으로 학원 모의고사의 난이도가 본 시험보다 쉽기때문에 모의고사에서 70점 이상을 받으셔야 합니다. 70점이 안되시는 분들은 앞서 말씀드린 '그냥' 시험보시는 분들에 속하게됩니다.

6. 감리원과 수석 감리원의 차이는?
○총괄 감리원(감리수행 시 대표 역할을 하는 감리원)은 수석감리원만 할 수 있습니다.
대부분의 감리의 경우 5명이 나가게 되는데 최근에는 5명 모두 수석 감리원으로 구성되는 경우가 많습니다. 당연히 보수에도 차이가있으나 감리업계에서 대부분이 수석 감리원이기 때문에 목표를 수석 감리원으로 하시는 것이 좋습니다
○아래는 감리원과 수석 감리원증을 받을 수 있는 자격입니다
수석 감리원 : 정보시스템 감리사, 정보관리기술사, 전자계산조직응용기술사
일반 감리원 : 정보통신기술사, 기사 7년, 산업기사 10년, SIS 1급 5년, CISA 5년(CISA의 경우는 ACTIVE자격입니다)

7. 시험 준비 기간은?
○최소 4개월 ~ 12개월 정도의 기간이 필요합니다
시간으로는 300 ~ 400시간 정도입니다
매일 3시간 이상 공부한다고 할때 3개월이 조금 넘는 기간입니다
하지만, 매일 3시간 공부하는 것이 절대 쉬운 일이 아닙니다. 주말포함해서 주당 20시간 정도의 시간인데, 꾸준히 하는 것이 중요합니다
참고로 기술사는 1,000시간 이상 학습해야 한다는 것이 정설입니다.
그럼 우리가 흔히 말하는 어떤 분야의 전문가라고 하는 사람들은 얼마큼의 시간을 투자했을까요?
10,000시간이라고 합니다. 매일 3시간씩 꾸준히 투자해서 약 9 ~ 10년의 시간이 필요한 기간입니다.
○얼마나 집중력 있게 학습하느냐에 따라 학습기간이 줄어 들 수 있구요
거듭 말씀드리지만 매주 20시간씩 꾸준하게 준비하셔야 합니다.
○학원의 경우 8 ~ 12주 정도의 교육 과정을 운영합니다. 교육 과정 이후에는 교육생간의 스터디 모임을 통해 학습 내용을 심화 시키게 됩니다

8. 어떻게 공부해야 하나요?
○첫째는, 모든 학습의 기본은 기출문제의 분석입니다.
현재 시험 문제가 공개된 4 ~ 8 회의 기출문제를 먼저 풀어보시고 꼼곰히 분석하여 어떤 주제의 문제들이 어떤 깊이로출제되었는지 반드시 분석해야 합니다. 특히 반복적으로 출제가 되는 주제들에 대해서는 철저히 학습을 하여야 합니다
○두번째는 기본지식에 충실히 해야 합니다.
대부분이 학원에서 제공하는 각 과목별 정리 자료나 기술사 학습 자료들을 통해서 암기를 하시지만, 개인적으로는 개론서를 정독하시기를 추천합니다. 아래는 개인적으로 추전하는 도서입니다.
감리 - 정보사회진흥원 홈페이지 자료 참조
사업관리 - PMP자격 관련 도서 (이러닝 교육자료 시 제공하는 도서 등)
소프트웨어 공학 - 최은만 교수, 소프트웨어 공학
데이타베이스 - 이석호 교수, 데이타베이스 시스템
시스템 구조 및 보안 등은 범위가 너무 넓어서 추천 도서 없음
*참고로 요즈음 도서관들은 거의 관외대출이 됩니다(2-3주)
대출증을 만드셔서 빌려보시면 됩니다)
○세번째는 모의고사의 풀이입니다. 적어도 1,000문제 이상 1,500문제 정도 풀어보셔야 합니다.

9. 감리사 시험 준비를 위한 학습 요령
○반드시 본인의 학습 내용과 시간을 엑셀로 관리하셔서 학습범위와 학습량을 지속적으로 체크해야 합니다
기록하지 않으면 관리할 수 없습니다. 내가 지금 무슨 공부를 얼마큼 했고, 모의고사를 통해서 점수가 부족한 과목이 어디인지에 대한 분석이 되어야 학습의 전술을 세울 수 있습니다.
시험에 떨어지신 분들은 아마도 학습시간이 300시간이 안될 것입니다. 만약 300시간이 넘는데도 불구하고 불합격했다면 학습내용과 방법의 문제입니다.
즉, 기록되지 않으면 실패했을때 원인이 나오지 않고 따라서 내년에도 또 실패할 가능성이 높습니다.
○시험 1-2주전에 반복적으로 학습할 본인만의 요약 정리집을 만들어야 합니다.
시험전에 시험장에 요약자료 없이 앉아 계신 분들이 있습니다. 3가지중에 한가지 경우입니다. 기술사분이시거나, 3번이상 기술사시험 응시 경험을 가지고 있고 기술사 모의고사에서 55점이상 나오는 일진 예비기술사분, 마지막으로 앞서 말한 '그냥'시험 보시는분
○스터디 그룹을 만들어서 함께 공부해야 합니다. 혼자서 공부하셔서 합격하시는 분들도 있지만, 대부분 스터디를 통해서 합니다. 그 이유는 정보의 습득/공유와 같이 공부하는 사람을 통한 지속적인 자극에 있습니다.
(간혹 스터디 그룹 전체가 악의 구렁텅이로 빠지는 경우도 있습니다. 무서운 경우 입니다. 만약 그럴 징조가 있으면 설사 추가비용이 수반된다 하더라도 스터디 그룹을 옮기셔야 합니다. 감리사나 기술사 공부는 나만의 문제가 아닙니다. 가족의 희생이 따르는만큼 결과에 책임을 지려는 최선의 노력이 필요합니다.)

10. 감리사와 기술사 중 어떤 자격증이 더 좋은 가요?
○두 자격증간에 마땅히 비교기준이 될 만한 척도가 없어서 단순비교에는 무리가 있습니다. 경제적인 측면에서 감리사가 더 좋다고하시는 분들도 있고, 존재이전 범위 측면에서 기술사가 더 좋다고 하시는 분들도 있고 막상막하라고 볼 수 있습니다.
○하지만 시험 준비에 있어서는 확실한 차이가 있습니다. 기술사 공부를 하신 분들은 조금만 준비하시면 감리사 시험에 응시하는데문제가 없지만, 감리사 공부를 하신 분들은 기술사 시험을 위해서는 처음부터 다시 준비를 해야 합니다. 그 이유는 기술사 시험이100% 논술형 시험이라는데 있습니다.
답안지를 작성해야 하기 때문에 같은 주제(토픽)라고 해도 공부해야 하는 내용과 정리해야 하는 내용이 완전히 다르기 때문입니다.
다만 감리사 시험이 7월이 되면서 기술사 시험이랑 가깝기 때문에(2월, 8월) 현실적으로 기술사 시험을 한달 여 앞두고 감리사 시험으로 전환을 해서 준비하는 것은 불가능합니다.
○혹 장기적으로 2가지를 다 고민하시는 분들은 기술사 공부를 쪽으로 방향을 잡으시는 것이 좀 더 효율적입니다

[출처 : 연탄한장의 블로그 (http://blog.naver.com/ytan1988)]

starcraft II 베타 플레이....

조금 무겁네요.....

정발에 최적화가 되어 있을 라나....

월드 어브 워크래프트 (Wow)의 매력적인 아가씨.....

마력이란....

Asteroids –This is a great Windows Mobile version of an equally great classic. If you don’t mind using 200KB of your mobile phone’s memory, this is a must-have.

BeMario – A simple clone of the 8-bit Super Mario game, BeMario offers even the iconic jump and coin-snatching sounds.

BombSquad – This is a cool game which clones an equally cool Windows game, Minesweeper.

Break My Bricks – This game was developed specifically for the HTC Touch Pro, but it works on other Pocket PCs. The game feature various options for sound, vibration and ball speeds and has increasing levels of difficulty.

Buggles - This is the classic plastic bubble game ported to the Windows Mobile phones. It features an authentic ‘pop’ and realistic graphics.

Butterfly – Match sets of three or more bubbles to rescue butterflies in this fun puzzle game.

Crazy Matrix – Try to get as many lights glowing as you can in this addictive puzzle game.

Dope Wars – Buy and sell dope in this strategy classic.

EdgeWay Turbo 21 – If you’re fond of playing cards, you’ll like this game. Exercise your mind to make as many blackjacks as possible. Just a little warning: this game can be pretty addictive.

Egoman- It’s everybody’s favorite retro game star wielding a gun? Replete with ghosts and power pellets, this is one entertaining PacMan-inspired shooter.

GravityBalls - This is a GSensor game about gravity and balls. Users adjust the gravitational force and smack the balls with a paddle. This game works on HTC Touch Diamond and HTC Touch Pro.

Halma Sharp – This is a Windows Mobile phone version of the 19^th century board game Halma. To win, move your pieces into the opponent’s corner.

Igrecway Hangman – Here’s hangman designed specifically for Windows Mobile phones. It features large dictionaries, hints and an iPhone-style interface.

Kevtris – Possibly the best Tetris clones ever released – this game features outstanding graphics, three difficulty levels, and high score sharing with other players.

Mu Torere – This is the Windows Mobile version of the all-time favorite Windows game, Reversi.

NetHack – This classic dungeon game has seen versions on DOS, Linux, Mac and Windows. There’s no reason it shouldn’t be on your Windows Mobile phone as well.

Next Element Delux – Here’s another cool logical game featuring 80 mind-twisting levels with interesting graphics and music.

NS Pairs – This is the Windows Mobile take on that the classic matching memory game.

PacMan – If you prefer the real thing, this is it. All the goodness of the classic PacMan game is here. It features full customization to add lives, change difficulty levels, and assigned buttons for control.

Pipes – Here’s a classic puzzle game featuring six difficulty levels. The object is to move around pipes and get water flowing to the flowers.

Pocket Lemmings – This is very similar to the original DOS and Amiga versions of the game.

Pocket Uno – This is a remake of the classic card game. It features multi-language support (English, Russian, Esperanto), three levels of computer play, auto-save, adjustable graphics, and stylus-free gameplay.

Pocketman – If you like PacMan, you’ll love this game. This remake features plenty of exciting levels, adjustable game speed and difficulty, fine sound and music, stylus and keyboard control, and the option to pause the game should you receive a call.

PocketMoku – Complete a continuous line of five stones in this remake of the classic puzzle game.

Project GD – This is a fun top-down shooter in the vein of Space Invaders.

Rawalls v1.4 – This simple, yet quite entertaining, puzzle game looks like a cross between minesweeper and Sudoko.

S3t! – This game was inspired by the classic SET card game. The game mechanics can be complicated unless if you’ve played SET.

Scrobble- This is very similar to Scrabble, outside of some minor differences. There are no challenges and players can only exchange all of their letters at once.

Smartfall – This is another Tetris clone running on Windows Mobile phones.

Snake – Here’s another popular game ported to Windows Mobile Phones. Who hasn’t played this game?

Snake.bizPla.net v1.0 – This is the Windows Mobile version of the classic game Snake. It features keyboard and stylus control as well as adjustable game speed.

Space Invaders – This is a remake of the 1978 classic. The developer made the game as close as possible to the original.

Spin The Bottle – If you have an HTC Diamond or HTC Touch Pro, you’ll enjoy spinning the bottle using your phone’s accelerometer.

Squares – This game offers simple gameplay with simple layout but definitely entertaining. All you have to do is avoid the squares for as long as you can.

Tic Tac Toe game – It’s tic-tac-toe ported for your WinMo-powered phone.

Touchtris – Enjoy the classic game of Tetris just by touching the screen.

VirusChaser- Prevent the virus from escaping by planting a wall. Every time you capture the virus, you have one less wall to prevent the virus from escaping.

Xonix – Move the spider as fast as you can to cut up a field and trap the monsters. This latest take on an arcade classic offers simple and addicting gameplay..

Xtrakt – This is a cool game built to run specifically on Sony Ericsson’s Xperia phone. But it on other Windows Mobile. In the game This game slay monsters while racing around on a motorcycle.

XWords for Pocket PC – Similar to Scrabble, this game features up to four players, move history, save game/open saved game, hints, tile protection and more.

소프트웨어 기술 경력증 고급

- 공부좀 해서 기술사나 되야 할텐데....

소프트웨어 기술 경력증 (고급)

MySQL Basics -- A Helpful MySQL Tutorial

Introduction

Welcome. This MySQL tutorial is a guide for new MySQL users, providing a reference of very basic, step by step, instructions on how to get started. This MySQL help page also gives more advanced users assistance in upgrading and running multiple versions of MySQL on a computer at the same time.

MySQL is an SQL based relational database management system (DBMS) that runs under a broad array of operating systems. MySQL is frequently used by PHP and Perl scripts. The SQL commands discussed in this tutorial apply to MySQL operating under all operating systems. Only the installation instructions are Windows specific. The focus is on Windows XP Professional and Windows 2000 Professional machines.

We'll be covering the installation of MySQL versions 5.0.51b, 4.1.16 as well as how to configure everything so they'll all be able to run on your system at the same time. Plus, the data directories will be moved to another location in order to make backups easier. If you only want to install one version of MySQL, ignore the instructions relating to the other versions.

If your operating system or versions of MySQL are different, the instructions should still work, but keep an eye out for slight differences, like which working directory you'll need to be in.

Usage:
Commands to type in and items that require appropriate substitutions are displayed like this.
Resulting screen text looks like this.
File names appear in this fashion.

Contents

• Windows 2000 and Windows XP Installation
  • Creating Command Prompt Shortcuts
  • Operating System Privileges for the MySQL Service
  • File System Permissions for the MySQL Directories
• Quick Tips for Other Windows Operating Systems
• Start the Client and Log In
• Tighten Security
• Creating a Simple Database and Displaying its Structure
• Putting Data into a Table
• Adding Fields
• Multi-line Command Entry
• Insert Some More Records into the Table
• Updating Existing Records
• Deleting Records
• Time to Call it Quits
• In Closing

Windows 2000, XP and NT 4.0 Installation

Log in to your computer using an account having Administrator privileges.

If you're not upgrading, just skip down to the next section.

If you are upgrading, there are MANY changes that you HAVE TO be aware of. Carefully read the pages in the MySQL manual that apply to you. If you intend to jump over a release series in your upgrade (e.g.: going straight from 4.0 to 5.0) you are strongly advised NOT to do so. You should do the upgrade process one release series at a time (e.g.: go from 4.0 to 4.1, then to 5.0).

• Upgrading from MySQL 5.0
• Upgrading from MySQL 4.1 to 5.0 (also includes several changes made between 5.0 versions)
• Upgrading from MySQL 4.0 to 4.1

Backup Old Data

Here's a quick rundown of how to save your old MySQL data so it can be used in your new system.

1. Open up a Command Prompt window. If you don't know how to do that, go to Start | Run, then type in cmd and hit ENTER.
2. Switch to the drive which has your present mysql\bin directory. Eg: L:\> C:
3. Move into the MySQL bin directory: cd mysql\bin
4. Dump all of your data: mysqldump -u root -p -A -r C:\secure\myolddata.sql
5. Stop the MySQL service: net stop mysql. If your service has a different name, do this net stop service_name.
6. The ISAM table format has been deprecated in 4.0 and removed from 5.0. If have some tables in that format, you'll need to fix that now. There are several ways to do this. Here are three possibilities:
   1. sed:
      1. ren C:\secure\myolddata.sql C:\secure\myolddataorig.sql
      2. sed 's/^) TYPE=ISAM/) TYPE=MyISAM/' C:\secure\myolddataorig.sql > C:\secure\myolddata.sql
   2. Perl:
      1. ren C:\secure\myolddata.sql C:\secure\myolddataorig.sql
      2. perl -wpe 's;^\) TYPE=ISAM;\) TYPE=MyISAM;i' < C:\secure\myolddataorig.sql > C:\secure\myolddata.sql
   3. Your favorite text editor: open C:\secure\myolddata.sql then do a search and replace on TYPE=ISAM to TYPE=MyISAM.
7. Remove the existing service by typing in mysqld --remove. If your service has a different name, do this mysqld --remove service_name
8. Jump up two directory levels: cd ..\..
9. Rename your old mysql directory as a backup: ren mysql mysqlold

Get and Install a Recent Version

1. Download the "Windows ZIP/Setup.EXE" file for the versions you want: 5.0, and/or 4.1. For now, do NOT pick the "Windows Essentials (x86)" or "Without installer (unzip in C:\)" downloads.
2. Find the downloaded file, unzip it and start the setup program:
   • Via Cygwin:
     1. cd /path/to/file
     2. unzip mysql-version.number-win.zip -d temp
     3. chmod 700 temp/*
     4. explorer temp
     5. Double click on Setup.exe.
   • Via Windows XP:
     1. Open up Windows Explorer. If you don't know how to do that, go to Start | Run, type in explorer and hit ENTER.
     2. Find the downloaded file.
     3. Double click on it.
     4. Windows XP has a built in zip file reader.
     5. In the zip viewer, double click on Setup.exe .
   • Via WinZip or PKZIP for Windows, or other such utilities:
     1. Open up Windows Explorer. If you don't know how to do that, go to Start | Run, type in explorer and hit ENTER.
     2. Find the downloaded file.
     3. Double click on it.
     4. Extract the files.
     5. Flip back to Windows Explorer and double click on Setup.exe .
3. In the Installation Program:
   • MySQL 5.0.x and 4.1.x:
     1. In the "Please select a setup type" step, click the "Custom" radio button, then "Next."

     2. The next step gives you choices of which components to install and where to install it.

        Click the "Change" button at the bottom right of the dialog box and put in C:\program files\mysql50\ then click "OK"

        If you're upgrading, make sure to click on the plus sign next to the "Developer Components" item, then click on "Scripts, Examples" and set it to "This feature will be installed on the local hard drive."

        Adjust the other entries per your desires. Make sure the "MySQL Server" and the "Client Programs" are selected. Once you have everything lined up as you want, click "Next."

     3. Click "Install."
     4. When you get to the "MySQL.com Sign-Up" step, let's cut to the chase... click the "Skip Sign-Up" radio button and go to "Next."
     5. UN-check "Configure the MySQL Server" and click "Finish."
4. Taking a moment to make Command Prompt shortcuts now will save loads of time later:
   1. Open Windows Explorer (Start | Run, explorer, ENTER).
   2. Navigate to C:\Documents and Settings\All Users\Start Menu directory.
   3. Create a new directory (File | New | Folder). That makes a new folder called, "New Folder" (imagine that!) which is now ready for you to type in a new name for. So, type in Databases and hit ENTER.
   4. Now hit ENTER again to get into that folder.
   5. Open another Windows Explorer window.
   6. In the Address Bar, type in %UserProfile% and hit the ENTER key. If the Address Bar isn't visible, in Windows Explorer's menu: View | Toolbars | Address Bar.
   7. Navigate to the Start Menu\Programs\Accessories directory.
   8. Select the Command Prompt file.
   9. Hit CTRL-C
   10. Now come back to the "Databases" folder window and hit CTRL-V. That should have pasted a copy of the Command Prompt shortcut in your new directory.
   11. Select the Command Prompt file.
   12. What you do here depends on whether you're installing 5.0 and/or 4.1.
       • MySQL 5.0.x:
         Use the follow these steps verbatim.
       • MySQL 4.1.x:
         Use these steps, but change 50 to 41.
       • Multiple versions:
         Do the steps for 50, make a copy of MySQL 50 Prompt and then follow steps I and II, but change 50 to 41.
       1. Hit the F2 key and rename the shortcut MySQL 50 Prompt then hit ENTER.
       2. Open it's properties via File | Properties and go to the "Shortcut" tab, then the "Start In" box and type the following in, including the quotes: "C:\program files\mysql50\bin"
       3. Go to the "Options" tab and check the "QuickEdit mode" and "Insert mode" boxes.
       4. Go to the "Layout" tab and go to the "Height" box in the "Screen buffer size" section and put in a larger number, like 2000.
       5. Click OK
   13. Now, you'll be able to quickly get to either of the Command Prompts by going to Start | Databases | MySQL 50 Prompt.
   14. Plus, you'll be able to paste commands into the the Command Prompt! To do that, copy the command from this tutorial (or wherever) then go to the Command Prompt window and hit the following keys:
       1. ALT-SPACE (to open the menu in the upper left corner of the window)
       2. E (the access key for Edit)
       3. P (the access key for Paste)
   15. For the rest of this lesson, we'll be calling this these the "MySQL 50 Shortcut" and "MySQL 41 Shortcut"
5. Time to create the data directories. MySQL's data files should be stored on a drive, or a portion thereof, that contains your other data files. This will simplify finding and backup up your information. The M: drive on my machine is dedicated solely to storing actively used data. That's the location we'll use in this tutorial.
   1. Open up a Command Prompt window. If you don't know how to do that, go to Start | Run, then type in cmd and hit ENTER.
   2. Switch to the drive where the data will be placed: C:\> M:
   3. Make the needed directories:
      • MySQL 5.0.x:

        mkdir mysql50mkdir mysql50\datamkdir mysql50\data\mysqlmkdir mysql50\ibdatamkdir mysql50\iblogs

      • MySQL 4.1.x:

        mkdir mysql41mkdir mysql41\datamkdir mysql41\data\mysqlmkdir mysql41\ibdatamkdir mysql41\iblogs

   4. Copy the default mysql database/privileges to the new location:
      • MySQL 5.0.x:

        copy "C:\program files\mysql50\data\mysql" mysql50\data\mysql

      • MySQL 4.1.x:

        copy "C:\program files\mysql41\data\mysql" mysql41\data\mysql

6. I suggest putting empty my.cnf files in place in order to keep your MySQL servers from being subverted. While this step isn't strictly necessary, it's better to be safe than sorry. We'll do this via the Command Prompt window we were using above.

   Be aware that Windows considers .cnf files to be a "SpeedDial" configuration file and automaticlaly hides the file extension. You can make the extension visible via Windows Explorer's "hide file extensions" option (Tools | Folder Options | View). Also note that Windows Server 2003 hides the extension even if this option is turned off.

   • Just MySQL 5.0.x:
     1. notepad mysql50\data\my.cnf
     2. In notepad, type in [mysqld] , save the file and exit.

     3. copy mysql50\data\my.cnf "C:\program files\mysql50\data"

   • Just MySQL 4.1.x:
     1. notepad mysql41\data\my.cnf
     2. In notepad, type in [mysqld] , save the file and exit.

     3. copy mysql41\data\my.cnf "C:\program files\mysql41\data"

   • All of the above
     1. notepad mysql50\data\my.cnf
     2. In notepad, type in [mysqld] , save the file and exit.

     3. copy mysql50\data\my.cnf "C:\program files\mysql50\data"copy mysql50\data\my.cnf mysql41\datacopy mysql50\data\my.cnf "C:\program files\mysql41\data"

7. The my.cnf configuration files need to be put in place. First, we'll put blank files in the default locations in order to prevent the server from potential subversion. Do this via the Command Prompt window we were using above.
   1. notepad C:\my.cnf

   2. In notepad, paste in the following, then adjust the the port numbers and drive letters and paths as needed.

      NOTE: This sample file puts 5.0.x on the default port (3306) and 4.1.x on 3341. These port numbers will be used throughout the rest of the tutorial. So, if you change anything in your my.cnf file, you will need to adjust all of our commands accordingly. On the command line, MySQL uses the -P flag to tell the client which port to connect to, for example -P 3341.

      # This config file contains settings for MySQL versions# 5.0.x and 4.1.x.  Be aware that only one server# instance can be on a given port.  This sample puts# version 5.0.x on MySQL's default port, 3306.  Adjust# the port numbers to suit your situation.[mysql]# Displaying the version number in the prompt# helps when running multiple instances.prompt = mysql\\_\v>\\_[mysqld-5.0]port = 3306basedir = C:/Program Files/mysql50/datadir = M:/mysql50/data/innodb_data_home_dir = M:/mysql50/ibdata/innodb_log_group_home_dir = M:/mysql50/iblogs/innodb_data_file_path = ibdata1:10M:autoextend# Make table names case sensitive.# Ensures portability when moving applications to other os's.set-variable = lower_case_table_names=0# Roll back entire transactions that time out,# OPTION AVAILABLE SINCE 5.0.32.innodb_rollback_on_timeout = 1[mysqld-4.1]port = 3341basedir = C:/Program Files/mysql41/datadir = M:/mysql41/data/innodb_data_home_dir = M:/mysql41/ibdata/innodb_log_group_home_dir = M:/mysql41/iblogs/innodb_data_file_path = ibdata1:10M:autoextend# Make table names case sensitive.# Ensures portability when moving applications to other os's.set-variable = lower_case_table_names=0

   3. Save the file and exit.
8. Next, we need to "install" the appropriate MySQL services.
   • MySQL 5.0: Open the MySQL 50 Shortcut, pick one of the following and type its command into the Command Prompt:
     1. NT/2000/XP. Named pipes.
        mysqld-nt --install mysql50
     2. Transactions.
        mysqld --install mysql50
     3. Support for debugging MySQL crashes.
        mysqld-debug --install mysql50
   • MySQL 4.1: Open the MySQL 41 Shortcut, pick one of the following and type its command into the Command Prompt:
     1. NT/2000/XP. Named pipes.
        mysqld-nt --install mysql41
     2. Transactions.
        mysqld --install mysql41
     3. Support for debugging MySQL crashes.
        mysqld-debug --install mysql50
9. Good security procedures call for running services as a non-privileged user. So, let's create such a user and configure the MySQL services to use it:
   1. net user mysql * /add /passwordreq:yes /passwordchg:no /comment:"runs MySQL services"
   2. You'll be prompted for the password.
   3. Perform the following steps for each mysql server instance, substituting your version numbers for the underscores (__):
      1. Start up the services manager by typing in services.msc and hitting ENTER.
      2. Locate the "mysql__" service in the right hand pane and double click it.
      3. Go to the "Log On" tab
      4. Click the "This account" radio button
      5. Type mysql into the box.
      6. Enter the password into the "Password" and "Confirm password" inputs.
      7. Hit OK

10. Let's lock down the file permissions on the directories we created by entering the following commands into a Command Prompt:
    cacls C:\my.cnf /g administrators:f system:r "authenticated users":r

    If you may get the following error message: The cacls command can only be run on disk drives that use the NTFS file system. Don't worry about it (for now). Skip all the cacls commands in the rest of our tutorial.

    Enter each line below separately because some of them require user confirmation.

    • MySQL 5.0.x:

      cacls M:\mysql50 /t /g administrators:f system:f mysql:ccacls M:\mysql50\data\my.cnf /t /g administrators:f system:rcacls "C:\program files\mysql50" /t /g administrators:f system:f mysql:r "authenticated users":rcacls "C:\program files\mysql50\data" /t /g administrators:f

    • MySQL 4.1.x:

      cacls M:\mysql41 /t /g administrators:f system:f mysql:ccacls M:\mysql41\data\my.cnf /t /g administrators:f system:rcacls "C:\program files\mysql41" /t /g administrators:f system:f mysql:r "authenticated users":rcacls "C:\program files\mysql41\data" /t /g administrators:f

11. Start the services:
    • MySQL 5.0.x: net start mysql50
    • MySQL 4.1.x: net start mysql41

    If System error 1069 has occurred comes up, your passwords didn't match. You can create a new password by typing net user mysql * into the Command Prompt. Then put that new password into the MySQL services' properties' "Log On" tab.

    Getting a System error 5 has occurred indicates problems getting to the directory containing the MySQL executables (for example, insufficient permissions).

    If you get an error saying System error 1067 has occurred it means a configuration directive in C:\my.cnf couldn't be processed. That can be due to a typographical error in the name or value of a setting. Similarly, the path referred to by the setting's value could be inaccessible due to insufficient permissions.

    To help narrow down what's going on, check out the Event Viewer: Start | Run, then type in eventvwr.msc and hit ENTER. Click the "Application" item in the left pane. Now examine the top of the right hand pane for recent MySQL errors. Double click the first item and look at the message in the "Description" box.

    Either of the following mean there's a boo-boo in the path value assigned to the datadir setting in C:\my.cnf:
    Fatal error: Can't open privilege tables: Table 'mysql.host' doesn't exist
    or
    Warning: Can't create test file
    In this situation, make sure the actual path is a case-sensitive match to the path in the configuration file and that the directories in question have the permissions they need to be accessed by the MySQL daemon. Then try the net start command again.

    Along the same lines, error logs showing Can't find messagefile 'C:\Program Files\mysql\share\english\errmsg.sys'
    points to a mismatch between the basedir value and the actual path to the MySQL executables.

    An unknown variable notice is clear enough, no?

    If there are no MySQL related error messages in the Event Log's Application section, you have a major typo in the C:\my.cnf. Perhaps one of the [mysql...] section headings are wrong.

12. If you're upgrading and followed our instructions at the top of this tutorial, now it's time to import your old data. These steps assume upgrading from 4.1 to 5.0.
    1. C:\Program Files\mysql50\bin> mysql -u root < C:\secure\myolddata.sql
    2. C:\Program Files\mysql50\bin> mysql -u root -f mysql < ..\share\mysql_fix_privilege_tables.sql

       This SQL file was in the scripts directory prior to version 5.0.38.

       You can ignore all of the query error messages (for example Unknown column, Duplicate column name, etc).

    3. Log into the server using the permissions from your old MySQL installation:
       C:\Program Files\mysql50\bin> mysql -u root -p mysql
    4. The upgrade script gives some privilges that you probably don't want most users having. Let's change them back (adjusting the "otherimportantusers..." below as needed for your system):
       mysql 5.0.51b-community-nt> UPDATE user SET Create_tmp_table_priv='N' WHERE user NOT IN ('root', 'otherimportantusers...');
    5. Exit the client and restart the server:
       mysql 5.0.51b-community-nt> exit
       C:\Program Files\mysql50\bin> net stop mysql50
       C:\Program Files\mysql50\bin> net start mysql50
    6. If you've never done this tutorial's "Tighten MySQL's Security" steps, below, check them out now. If you've already done them, you can jump down to the Start the Client section.
13. Tighten MySQL's Security

    MySQL has good security controls, but the default installation is wide open. So, if you're doing a new installation, let's close things up before we go any further.

    In the following commands, don't forget that if you changed the ports in the my.cnf file, you'll have to adjust the port numbers here.

    • MySQL 5.0.x:

      Activate the "MySQL 50 Shortcut" we created earlier then type in:
      mysql -u root mysql

    • MySQL 4.1.x:

      Activate the "MySQL 41 Shortcut" we created earlier then type in:
      mysql -u root -P 3341 mysql

    (If you get the following error message:
    ERROR 2003 (HY000): Can't connect to MySQL server on 'localhost' (10061)
    That means the servers didn't stay started. The most likely reason is the my.cnf file has errors in it. Go back to the Start the services step and carefully read the section about checking the Event Viewer logs.)

    Once you are logged in, copy the following queries to Notepad and change NewPw to something unique. Now copy that and paste it into the command prompt window(s) you just opened.

    delete from user where Host <> 'localhost' and User <> 'root';delete from db;update user set Password=password('NewPw') where User='root';flush privileges;exit

14. Tada!

Quick Tips for Other Windows Operating Systems

If you're using Windows 95, 98 or ME do not run mysqld --install. These operating systems don't have the ability to host a "service." So, you need to run MySQL as a standalone application by executing the command mysqld --standalone.

I haven't run MySQL on these systems myself, so, for more information, check out the Starting MySQL on Windows 95, 98 or Me and Running MySQL on Windows sections of the manual or explore the MySQL Win32 Mailing List Archive.

Start the Client and Log In

We'll be using MySQL 5.0.x here. Adjust the shortcut and port as necessary.

Activate the "MySQL 50 Shortcut" we created earlier and type in
mysql -u root -p
then enter your password when prompted. You will then see the following output:

Welcome to the MySQL monitor.  Commands end with ; or \g.Your MySQL connection id is 1 to server version: 5.0.51bType 'help;' or '\h' for help. Type '\c' to clear the buffer.

If your root account doesn't have a password on it, the above command won't work for you. You really need to get on top of security. Log in without the password:

mysql -u root mysql

Then set a password (changing "NewPw", of course):

update user set Password=password('NewPw') where User='root';flush privileges;

If you get an error saying Client does not support authentication protocol requested by server; consider upgrading SQL client when trying to connect, that means your client is from before version 4.1 while the server you are connecting to is using version 4.1 or later. The best solution is to install a current version of the MySQL client.

Creating a Simple Database and Displaying its Structure

Instruct MySQL to setup a new database

Database "database01" created.

All that really does is create a new subdirectory in your M:\mysql50\data directory.

Open the database

Database changed

Create a table

Query OK, 0 rows affected (0.00 sec)

Enclose entire list of field names between one pair of parentheses.
Commas are used between each field.
A space may be used after the comma between fields.
A comma is not used after last field.
This, and all SQL statements, are concluded by a semicolon ";".

List the tables

+----------------------+| Tables in database01 |+----------------------+| table01              || table02              |+----------------------+

List the fields in a table

+---------+----------+------+-----+---------+-------+| Field   | Type     | Null | Key | Default | Extra |+---------+----------+------+-----+---------+-------+| field01 | int(11)  | YES  |     |         |       || field02 | char(10) | YES  |     |         |       |+---------+----------+------+-----+---------+-------+

Congratulations! Pretty straightforward, eh?

Putting Data into a Table

Insert a record

Query OK, 1 row affected (0.00 sec)

Enclose entire list of field names between one pair of parentheses.
Enclose the values to be inserted between another pair of parentheses.
Commas are used between each field and between each value.
A space may be used after the comma between fields.

List all the records in a table

+---------+---------+| field01 | field02 |+---------+---------+|       1 | first   |+---------+---------+

Excellent!

Adding Fields

...one field at a time

Query OK, 1 row affected (0.04 sec)Records: 1  Duplicates: 0  Warnings: 0

...more than one at a time

Query OK, 1 row affected (0.04 sec)Records: 1  Duplicates: 0  Warnings: 0

The "add column" must be restated for each column.
Commas are used between each add column statement.
A space may be used after these commas.

The MySQL Manual fully explains each possible column data type.

Did it work?

+---------+---------+---------+---------+---------+| field01 | field02 | field03 | field04 | field05 |+---------+---------+---------+---------+---------+|       1 | first   | NULL    | NULL    | NULL    |+---------+---------+---------+---------+---------+

Multi-line Command Entry

The MySQL command line interface allows you to put a statement on one line or spread it across multiple lines. There's no difference in syntax between the two. Using multiple lines allows you to break down the SQL statement into steps you may more easily comprehend.

In multiple line mode, the interpreter appends each line to the prior lines. This continues until you enter a semicolon ";" to close out the SQL statement. Once the semicolon is typed in and you hit enter, the statement is executed.

Here's an example of the same exact SQL statement entered both ways:

Don't break up words:

When inserting or updating records, do not spread a field's string across multiple lines, otherwise the line breaks are stored in the record:

+---------+---------------------+| field01 | field02             |+---------+---------------------+|    NULL | Who thought of foo? ||    NULL | Pooh thoughtof foo. |+---------+---------------------+

Insert Some More Records into the Table

Add this record

Query OK, 1 row affected (0.00 sec)

Quotes must go around text values.

Standard date format is "yyyy-mm-dd".
Standard time format is "hh:mm:ss".
Quotes are required around the standard date and time formats, noted above.
Dates may also be entered as "yyyymmdd" and times as "hhmmss". If entered in this format, values don't need to be quoted.

Numeric values do not need to be quoted. This holds true regardless of the data type a column is formatted to contain (e.g. text, date, time, integer).

MySQL has a useful command buffer. The buffer stores the SQL statements you've entered thus far. Using it keeps you from having to retype the same commands over and over. Let's use this next step as an example.

Add another record using the command buffer (and optional date and time formats)

1. Hit the up arrow key twice.
2. Hit the ENTER key.
3. Type in the new values between a pair parentheses and stick a closing semicolon on the end.
   (3, 'a third', 'more foo for you', 19991024, 103004);
4. Hit the ENTER key.

Voilà!

Is it in there?

+---------+-----------+------------------+------------+----------+| field01 | field02   | field03          | field04    | field05  |+---------+-----------+------------------+------------+----------+|       1 | first     | NULL             | NULL       | NULL     ||       2 | second    | another          | 1999-10-23 | 10:30:00 ||       3 | a third   | more foo for you | 1999-10-24 | 10:30:01 |+---------+-----------+------------------+------------+----------+

It's in there!

Now, we're almost done...

Updating Existing Records

Modify one field at a time

Again, be careful with syntax. Quote marks need to go around text but not around numbers.

Query OK, 1 row affected (0.00 sec)

Change multiple fields at once

Remember to put commas between each field you're updating.

Query OK, 1 row affected (0.00 sec)

So, what's up with our data?

+---------+-----------+------------------+------------+----------+| field01 | field02   | field03          | field04    | field05  |+---------+-----------+------------------+------------+----------+|       1 | first     | new info         | 1999-10-22 | 06:22:18 ||       2 | second    | another          | 1999-10-23 | 10:30:00 ||       3 | third one | more foo for you | 1999-10-24 | 10:30:01 |+---------+-----------+------------------+------------+----------+

Update multiple records in one stroke

Query OK, 3 rows affected (0.00 sec)

Survey says...

+---------+-----------+------------------+------------+----------+| field01 | field02   | field03          | field04    | field05  |+---------+-----------+------------------+------------+----------+|       1 | first     | new info         | 1999-10-22 | 15:29:01 ||       2 | second    | another          | 1999-10-23 | 15:29:01 ||       3 | third one | more foo for you | 1999-10-24 | 15:29:01 |+---------+-----------+------------------+------------+----------+

Wee haw!

Deleting Records

The delete command

Query OK, 1 row affected (0.01 sec)

+---------+---------+----------+------------+----------+| field01 | field02 | field03  | field04    | field05  |+---------+---------+----------+------------+----------+|       1 | first   | new info | 1999-10-22 | 15:29:01 ||       2 | second  | another  | 1999-10-23 | 15:29:01 |+---------+---------+----------+------------+----------+

Time to Call it Quits

Bye

In Closing

Now you know some rudimentary commands for running a database in MySQL. Since MySQL is operated by executing SQL calls, you have a broad array of very powerful tools at your disposal. For instance, you're able to display data from several tables at once by joining related fields.

Similarly, SQL permits complex displays, updates or deletions of multiple records which fit specific criteria. So, your next step toward mastery is learning all about SQL.

James Hoffman has put a tutorial page up on the web entitled Introduction to Structured Query Language.

Another thing to note is MySQL offers good security features you'll need to use when operating on networks.

To learn more about MySQL and how to use it, the manual should be your first stop. Also, Paul DuBois' book, MySQL, comes highly recommended. In addition, the archives of the main list and the Win32 list are tremendous resources. The NYPHP user group has started a MySQL interest group you may find helpful.

If you're curious about database portability, you may find the Building Truly Portable Database Applications in PHP presentation interesting.

If you'll be developing hypertext interfaces to your databases using PHP, check out our SQL Solution™. It's a powerful, user friendly, platform independent API that will make your job a snap! Similarly, you might want to examine PEAR DB, a popular open source database abstraction layer (of which I'm the lead developer).

Also, if your scripts accept user input, the Form Solution™ is a handy tool for cleaning user input, generating HTML / XHTML compliant date/time form elements, validating and formatting date/time inputs and holding all variables submitted by a form. The result is improved security and data quality.