Total Pageviews

Wednesday 29 February 2012

U must learn in testing



I must learn in testing:
Complete Software Development Life Cycle (Module Testing, Integration Testing, System Testing etc)
Bug tracking & Analysis
Testing methods like System Testing, GUI Testing, Functional Testing, Integration Testing, Browser Testing, Positive & Negative Testing End to End Regression Testing, Web application Testing, Black box testing.

Agile Environment
SQL and RDBMS concepts
Validation, Traceability and Analytical skills


1.       Integration Testing:
Steps for
Create a test plan
Create test cases and TEST DATA
If applicable script run to test cases
What’s the component have been integrated execute the test cases
Fix the bugs if any retest the code
Repeat the test until the component have been successfully completed


2.       System Testing

System testing in first level in SDLC
System testing is to verify functional and technical requirement


3.       Manual Testing, QTP, Bugzilla, QC, , automation testing, software testing, Test plans, test case, functional testing.

Automation Tester needs clarification on 3 main things
1.       Functional knowledge
2.       Functional criteria
3.       Analyze 
    
   1. Module Testing:Also known as unit or component testing phase, module testing is concerned with the testing of the smallest piece of software for which a separate specification exists.
In WebSphere Integration Developer, you can use the integration test client to test your modules and components and report the results of your test. The testing is generally performed on the interface operations of your components, which enables you to determine whether the components are correctly implemented and the references are correctly wired. However, you can also test event definitions to ensure that they are emitting common base events correctly.
Using the integration test client, you can test:
  • An individual module
  • A set of interacting modules
  • An individual component
  • A set of interacting components
2. Integration testing : Integration testing (sometimes called Integration and Testing, abbreviated "I&T") is the phase in software testing in which individual software modules are combined and tested as a group. It occurs after unit testing and before validation testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing.
Integration testing is a logical extension of unit testing. In its simplest form, two units that have already been tested are combined into a component and the interface between them is tested. A component, in this sense, refers to an integrated aggregate of more than one unit. In a realistic scenario, many units are combined into components, which are in turn aggregated into even larger parts of the program. The idea is to test combinations of pieces and eventually expand the process to test your modules with those of other groups. Eventually all the modules making up a process are tested together. Beyond that, if the program is composed of more than one process, they should be tested in pairs rather than all at once.
Integration testing identifies problems that occur when units are combined. By using a test plan that requires you to test each unit and ensure the viability of each before combining units, you know that any errors discovered when combining units are likely related to the interface between units. This method reduces the number of possibilities to a far simpler level of analysis.
You can do integration testing in a variety of ways but the following are three common strategies:
  • The top-down approach to integration testing requires the highest-level modules be test and integrated first. This allows high-level logic and data flow to be tested early in the process and it tends to minimize the need for drivers. However, the need for stubs complicates test management and low-level utilities are tested relatively late in the development cycle. Another disadvantage of top-down integration testing is its poor support for early release of limited functionality.
  • The bottom-up approach requires the lowest-level units be tested and integrated first. These units are frequently referred to as utility modules. By using this approach, utility modules are tested early in the development process and the need for stubs is minimized. The downside, however, is that the need for drivers complicates test management and high-level logic and data flow are tested late. Like the top-down approach, the bottom-up approach also provides poor support for early release of limited functionality.
  • The third approach, sometimes referred to as the umbrella approach, requires testing along functional data and control-flow paths. First, the inputs for functions are integrated in the bottom-up pattern discussed above. The outputs for each function are then integrated in the top-down manner. The primary advantage of this approach is the degree of support for early release of limited functionality. It also helps minimize the need for stubs and drivers. The potential weaknesses of this approach are significant, however, in that it can be less systematic than the other two approaches, leading to the need for more regression testing.
  • Integration testing, also known as integration and testing (I&T), is a software development process which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution. Integration testing is a component of Extreme Programming (XP), a pragmatic method of software development that takes a meticulous approach to building a product by means of continual testing and revision.
    There are two major ways of carrying out an integration test, called the bottom-up method and the top-down method. Bottom-up integration testing begins with unit testing, followed by tests of of progressively higher-level combinations of units called modules or builds. In top-down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that. In a comprehensive software development environment, bottom-up testing is usually done first, followed by top-down testing. The process concludes with multiple tests of the complete application, preferably in scenarios designed to mimic those it will encounter in customers' computers, systems and networks.
    3. System Testing :

    System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. [1]
    As a rule, system testing takes, as its input, all of the "integrated" software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limited type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.

    System Testing


    Testing the behavior of the whole software/system as defined in software requirements specification(SRS) is known as system testing, its main focus is to verify that the customer requirements are fulfilled.
    System testing is done after integration testing is complete. System testing should test functional and non functional requirements of the software.
    Following types of testing should be considered during system testing cycle. The test types followed in system testing differ from organization to organization however this list covers some of the main testing types which need to be covered in system testing.

    System Testing: Why? What? & How?

    Introduction:

    Unit testing’ focuses on testing each unit of the code.
    Integration testing’ focuses on testing the integration of “units of code” or components.
    Each level of testing builds on the previous level.
    ‘System Testing’ is the next level of testing. It focuses on testing the system as a whole.
    This article attempts to take a close look at the System Testing Process and analyze:
    Why System Testing is done? What are the necessary steps to perform System Testing? How to make it successful?


    4. A bug tracking system is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work. It may be regarded as a type of issue tracking system.
    Many bug-tracking systems, such as those used by most open source software projects, allow users to enter bug reports directly. Other systems are used only internally in a company or organization doing software development. Typically bug tracking systems are integrated with other software project management applications.
    Having a bug tracking system is extremely valuable in software development, and they are used extensively by companies developing software products. Consistent use of a bug or issue tracking system is considered one of the "hallmarks of a good software team"

No comments:

Post a Comment