Home | Help | Sign in 

Search Toolkit

Search

Software Testing
Software testing, Theory, ISTQB, Interview based theory, Manual & Automation Test process, QTP, Loadrunner, Quality center, Software testing life cycle and terminology Software testing - Complete Theory. A very detailed study & use of Software Testing from 199Os to 2008 has been digested about by several Major software companies and is evident in modern testing methodology. The following C T T (Concise testing thory) course should be of sufficient help to clear an I.T. interview for software testing engineers, QA, Automation and Manual Test management team and Performance testers alike. From manual to QTP, Load runner & Test management, the ever evolving testing field is drawing more and more attention lately. Its a very high paying field in IT and has lot of opportunity. Lets discuss everything that makes Software testing such an interesting topic. Contents
Software Testing Theory Index
¡ ¡ ¡ ¡ ¡ ¡

Edit this knol

Write a knol

Vinayak Rao
Musician, Software tester, Googler at officialiwant.com India

Article rating: Your rating:
No rating

0 Ratings

Software Testing? Who can do testing & things to understand ( Pre requirement to understand Software testing effectively) Software Development Life Cycle (SDLC) Software Testing Methods & Levels of Testing. Types of Testing: Sub Index : Link less more Citation Email Print Listen mp3 Favorite Collect this page

Moderated collaboration Creative Commons Attribution 3.0 License Top Viewed Knol Award Top Pick Knol Award Version: 93 Last edited: Mar 14, 2009 3:20 AM.

Versions

Software Testing Theory Index
Software Testing Complete Theory  Environments Software testing life cycle Bug life cycle ISTQB Chapters  ISTQB Tests & Answers References Save your Eyes : Green Search Engine: Testers approved   Let me start with a short Intro, I am a Self employed Musician and web developer, and have spent lot of time understanding the software testing field and the stages of evolution in it. And I bring in front of  you a very effective small dose of testing theory. (Thanks to Mr Suresh Reddy, My senior mentor at NRSTT Hyderabad for al the guidance and coaching. ) I have divided the Concise Testing Theory ( C.T.T ) into the following sections.  

Reviews
Be the first to review this knol

Vinayak Rao also wrote
Microsoft CRM Software Testing Life Cycle Mumbai need to strike back : 26/11 terror attacks How to make Software testing as easy as ABC - Entry to Knol for Dummies Contest ISTQB Certification, Answers of All tests Chapter 1-6 (18 knols and collections)

Related Knols
Web Software Testin... by Ed Seward Software Testing by Akber Choudhry Testing Fundamentals by Saravanan Thiruna... Software testing by d venkata suresh Program Testing by Beya Adamu

Sections
What is Software Testing ?  Who can do it? & Terminology. Software Development Life Cycle ( SDLC.) T esting methodology & Levels of testing. T ypes of Testing. Software Testing life cycle Bug life cycle (BLC.) A utomation Testing. Performance Testing. Validation & Verification of any task can be called as Testing (1)  I STQB & Software Certification   Each section is explained in Detail and will be enhanced as and when needed. Good luck and enjoy the syllabi. I will shortly create concise knols on Sql server & QTP. I do Believe Strongly that A good understanding of CTT can get you a job in IT ( at least in India, US, UK & AU) very soon. All you need minimum is to be A graduate from any field ( 15 years of formal  education).   

Knol translations
Help translate this knol into your language. Search for uses of this page ▼

Categories
Automation testing, Internet, ISTQB, reference, science, software Based on community consensus. Sign in to add or vote for categories Learn more about categories

Software Testing?
Testing in general, is a process carried out by individuals or groups across all domains, where requirements exist. Whereas, In more software subjective language, The comparison of E V (expected value ) and A V (Actual value) is known as testing.  To get a better understanding of the sentence above , lets see a small example,

Activity for this knol

but this had disadvantages .  ( An Interview definition. are the foundations for future's interactive web generation.       I  used so much of background to stress quality because Its the final and direct goal of Quality  assurance people or Test engineers. Terra bytes of  memory and bandwidths of  hundreds  of M bps.   l Defect can be defined as deviation from a users requirement in a particular product or service. Previously developers used to test the applications besides coding. Its the reality of tomorrow and a necessity to be learnt for healthy survival in the coming technological era.  But we have to understand the importance of software testing first. All you have to get in your mind is that your job is to act like a third person or end user and taste (test) the food before they eat. and Networking bandwidths was a  gen next topic. So My next step is to identify three things Action to be performed  : turn the Switch on. ideally based on the difference or margin of difference between the EV and AV . else Any deviation will make the result as FAIL. We need to realize that Software is here to stay and become a  part of mankind. IF EV = AV then the result is PASS . Anyone can do it. Expected value                   : Bulb should glow.   Public activity feed Flag inappropriate content Some Important terminologies l Project :  If something is developed based on a particular user/users requirements. ). We are not correcting the mistake here.  Now .       As a result . The Severity of the defect is  decided and is subjected for further rectifications. Product :  If something is developed based on company's specification (after a general survey of  l . Like time consumption . So as you can see that quality is a much wider requirement of the masses when it comes to consumption of any service. Developers are under constant pressure of learning and  updating themselves with the latest programming languages to keep up the pace with user's requirements. Hardware was costly and was very limited in its capacity to perform continuous tasks. that testing is a very general task and can be performed by anybody. So  the same product have different level of defects or No defects based on tastes and requirements of  different users.      So Finally Testers have been appointed to simultaneously test the applications along with the  development .  But Now Object oriented Programming languages. Isolated and then  subjected for rectification and Re ensuring that the end result is defect free (highest quality) in order to  achieve maximum customer satisfaction. emotional block to find defects in one's own creation and Post delivery maintenance which is a common requirement now. In the earlier days of software development. You need to be a graduate to enter software testing and  comfortable relationship with the PC. The finance is arranged by the client to complete the project successfully. we are only identifying the defects and reporting it and waiting for the next release to check whether the defects are rectified and also to see whether new defects have raised.   l Quality can be defined as Justification of all of the user's requirements in a product with the presence of value & safety. Sites like Google.( on or off ). Conferencing and Data management etc. MSN and Yahoo make life much easier to live with Chat . it should glow. More and more companies are spending billions of  cash for achieving the  limits and in all these process one thing is attaining its place more prominently which is none other than QUALITY.      Conclusive Definition of Testing :         Testing can be defined as the process in which the defects are Identified. Actual value                        : Present Status of the bulb after performing the action . IT sector has become sufficient enough to develop advanced software programming for even space exploration. Commercially very few rich companies used advanced software solutions. and report it to the developer. In order to identify defects as soon as possible to reduce time loss and improve efficiency of the developers. Testing is also becoming an Integral part of Software companies to produce quality  results for beating the competition. As more and more business solutions are moving from man to machine . then it is known as project. Now its the time for our test to generate a result based on a simple logic.   This week: 427 pageviews Totals: 25677 pageviews 17 comments Who can do testing & things to understand ( Pre requirement to understand Software testing effectively)          As we have understood so far. So the Job of a Tester is to act like a user and verify the product Fit ( defect free =  quality ). As three decades of research and development has passed .       Who can do it?  Well. and is used  exclusively by them.                  So coming back to our goal (testing) .            Programming languages in the beginning were very complex and were not feasible to achieve  larger calculations. and my requirement is that when i switch it on. the support for developing the programs was very little.example 1.  I have a bulb . both development and testing are headed for an unprecedented boom.

test data.                 Process : First the BA will take an appointment with the customer. version no. dissected into four parts individually.      SCM : Software configuration management : This is a process carried out by a team to attain the following things Version control and Change control . group. Whereas Impact analysis is a study carried out by the business analysts to gauze . l l l l l l l l l l l l l l l l       Software Development Life Cycle (SDLC)         This is a nothing but a model which is used to achieve efficient results in software companies and  consists of 6 main phases.    Common Repository : Its a server accessible by authorized users . In other words whether the developed service meets all the requirements or not.. The advantages of template is to maintain uniformity and easier comprehension. Change Request v/s Impact Analysis : Change request is the proposal of the customer to bring some changes into the project by filling a CRT ( change request template). The company has to fund the entire development and usually expect to break even after a successful market launch. SRN ( Software Release Note ) : Its a note prepared  by the development department and sent to the  testing department during the release and it contains information about Path of the build. . But If the product is  functionally non usable . such as Tasks. Slippage : The extra time taken to accomplish a task is known as slippage Metrics v/s Matrix : Clear measurement of any task is defined as metrics. how much impact will fall on the already developed part of the application and how feasible it is to go ahead with the change or demands of the customer.     Quality Assurance Verification : It is the method to check whether the developed product or project has followed the right process or guidelines through all the phases of development. Remember SDLC is similar to waterfall model where the output of one phase acts as the input for the next phase of the cycle. We will discuss each stage in a descriptive fashion. throughout all the documentation in a Project. Quality Assurance : Quality assurance is a process of monitoring and guiding each and every  role in the organization in order to make them perform their tasks according to the company's process guidelines. SDN ( Software delivery Note ) : Its a note prepared by a team under the guidance of a Project manager. then we say that The product has a defect. Template v/s document : Template is a pre-defined set of questionnaire or  a professional fill in  the blanks set up . which is used to prepare an finalize any document. Installation information. l Defect v/s Defective : If the product is justifying partial requirements of a particular customer but is usable functionally.the market requirements) and can be used by multiple set of masses.          Initial     phase      Analysis phase      Design    phase     Coding    phase     Testing   phase     Delivery and  Maintenance           Initial-Phase/ Requirements phase :     Task     :     Interacting with the  customer and gathering the requirements     Roles    :    Business Analyst and   Engagement Manager (EM). It contains a carefully crated User manual and list of known issues and workarounds. and will be submitted to the customer during delivery. then even if some requirements are satisfied. whereas a tabular format with linking information which is used for tracing any information back through references is called as Matrix. well in advance.      NCR : Whenever the role is not following the process in performing the task assigned. Base lining vs publishing : Its a process of finalizing the documents vs making it available to all the relevant resources.      Audit : Audit is a process of checking conducted on the roles or a department with a prior notice. then it is known as a product. department . Process and Proof of each phase completion. date and credentials etc. and also name the project and update its version numbers by gauzing the amount of change in the application or service after development. to store and retrieve the information safely and securely. the product still will be tagged as Defective. company or even larger masses. Release : Its a process of sending the application from the development department to the testing department or from the company to the market. Quality Control or Validation : To check whether the end result is the right product. In other terms SCM team is responsible for updating all the common documents used across various domains to maintain uniformity.      Inspection : Its a process of checking conducted by a group of members on a role or a department suddenly without any prior intimation. then the penalty given to him is known as NCR ( Non Confirmacy raised). list of known issues. Roles .

gathers requirements and comes back to the company with the requirements document. Get the prototype ( dummy.D)                       :    Low level Designing   (L.L. URS : User Requirement Specifications. After that in the next step we move to a temporary scheduling of staff to initiate the project. BRS : Business Requirement Specifications.)                                                   Coding Phase :     Task :     Developing the programs       Roles:     Developers/programmers   Process : The developers will take the support of technical design document and will be following the coding standards. meets the customer . and also deal with any excess cost of the project. Select a s u i t a b l e t e c h n o l o g y t o d e v e l o p t h e p r o j e c t e f f e c t i v e l y Analysis Image references see below  ( customer's choice is given first preference .   Proof                :         T h e   p r o o f   d o c u m e n t   o f   t h e   a n a l y s i s   p h a s e   i s  S R S ( S y s t e m R e q u i r e m e n t Specification. Color coding. while actual source code is developed. Commenting etc. similar to end product) developed in order to get exact details in the case of unclear requirements or confused customers.SDLC Image See references below  Collects the requirement template.                                             Testing Phase :     Task     : Testing     Roles    : Test engineers. The Technical lead will further divide those modules into sub modules using UML .L. we will look at a descriptive fashion of understanding the .  Then the EM will go through the requirements document .) and developing the Pseudo code (A dummy code Or usually.   Alternate names of the Requirements Document : (Various companies and environments use different terminologies.D)       Roles    :    Chief Architect ( handle HLD )                      :    Technical lead ( involved in LLD)   Process :    The Chief Architect will divide the whole project into modules by drawing some graphical  layouts using Unif[ied Modeling Language (UML). Some of the Industry standard coding methods include Indentation.                            Technology selection                            Requirement analysis       Roles    :    System Analyst (SA)                           Project Manager (PM)                             Technical manager (TM)        Process  :         A   d e t a i l e d   s t u d y   o n   t h e   r e q u i r e m e n t s   a n d   judging the possibilities and scope of the requirements is known as feasibility study.)                                                    Design Phase :     Tasks    :    High level Designing (H.               And Finally the Hardware. And both will be responsible for visioning the GUI ( The screen where user interacts with the application OR Graphical User Interface .   Process : Since It is the core of our article . BD : Business Document. But the logic is same ) FRS  : Functional Requirements Specification.                                                  Analysis Phase :     Tasks    :    Feasibility Study. software and  Human resources required are listed out in a document  to baseline the project. Quality Assurance team.                             Tentative planning. Try to find additional requirements .   Proof : The Requirements document is the proof of completion of the first phase of SDLC . BDD : Business Design Document. CRS : Customer/Client Requirement Specification. It is done by the Manager level teams usually. Its a set of English Instructions to help the developers in coding the  application.   Proof :  The proof document of the coding phase is Source Code Document (SCD). If it is feasible ).

It's an old way of testing and is not as effective as the previous two methods and is losing popularity recently. Black Box. If at all they find any defects.    There are three methods of testing . they will execute the test cases.   .                                        (The  ticked options are the ones where Black box testers are required and the                                            other performed by the developers usually). related defects.                   Maintenance : Once the application is delivered the customer will start using the application. Testers will here check for the previous defects. Some customers may be expecting continuous maintenance.      Levels of Testing There are 5 levels of testing in a software environment. Let's see. While executing the test cases . While using if any problem occurs . then that method of testing is known as Black box testing. Based on the severity of the issue corresponding roles and process will be formulated. the developers will be notified of the status of the defect.                Unit level testing:  A unit is defined as smallest part of an application. Business Analyst ) in order to get the clarifications. l l l l l l l Proof : The last two steps are carried out till the product is defect free . In that case a team of software engineers will be taking care of the application regularly. they will report it in the Defect Profile Document or DPD. Usually test engineers are in this category. new defects and update the DPD. Usually developers or white box testers are the ones to do it successfully. so quality assured product is the proof of the testing phase ( and that is why it is a very important stage of SDLC in modern times). Once the clarifications are done and sent to the testing team. They are as follows.testing process in an I T environment. then it becomes a new task. While revising .   l First. In this level of testing. If at all any doubts arise. And also update the status of defects in the DPD. Once the defects are sorted out.                                          I m age: Systematic & Simultaneous Levels of testing. Usually the white box testers or developers are the performers at this level.       Black Box testing   :   If one performs testing only on the functional part of an application  (where end users can perform actions) without having the structural knowledge. White Box & Grey box testing.        Software Testing Methods & Levels of Testing.e. then that method of testing is known as Grey box testing. then the testers will list out all the unclear requirements in a document named Requirements Clarification Note (RCN). Then they send the RCN to the author of the requirement document ( i. ( test cases like example1 above). they will take the test case template and write the test cases.         Grey Box testing   :    If one performs testing on both the functional part as well as the structural  part of an application. the development team releases the next build for testing. Once the first build is released. Since the DPD is in the common repository.                                               Delivery & Maintenance phase     Tasks     : Delivery                         : Post delivery maintenance       Roles     : Deployment engineers   Process : Delivery : The deployment engineers will go to the customer environment and install the application in the customer's environment & submit the application along with the appropriate release notes to the customer . each  and every program will be tested in order to confirm whether the conditions. the Requirements document will be received by the testing department l l The test engineers will review the requirements in order to understand them.         White Box testing   :   If one performs testing on the structural part of the application then that  method of testing is known as white box testing. functions and loops etc are working fine or not.

 Balance inquiry screen. testing will be carried on.    Build Acceptance Test/Verification/Sanity testing (BAT) : Its a type of testing in which one will perform an overall testing on the application to validate whether it is proper for further detailed testing. not only features .       Other two terms Smoke testing and Sanity testing are in debate from time immemorial to find a fixed  definition. the test engineers will perform many different types of testing.       Initially there were very few popular types of testing. load. Usually.     Big Bang approach: In this approach one wait till all the modules are developed and integrate them finally at a time. and features like GUI and appearance related testing comes under this category. the result is PASS.Module level testing: A module is defined as a group of related features to perform a major task.   System: Once the stable complete application is installed into an environment.    Bottom up approach: In this approach the child modules will be developed first and will be integrated back to the parent modules. Majority feel that If developers test the overall application before releasing to the testing team for further action is known as Smoke testing and future actions performed by black box test engineers is known as Sanity testing. but the most Important  one is. if at all any mandatory module is missing. functionality and appearance but performance and stability also are major areas to be concentrated.          Types of Testing:     There are two categories broadly to classify all the available types of testing software. They are Static testing & Dynamic testing. Usually testing team conducts this in high risk applications before accepting the application from the development department. Its inevitable that.      Example 2:  Let's take An ATM machine application. And Dynamic is where user needs to perform some actions on the application to test like functionality checking.  Welcome screen. Whatever user may desire. Its the final testing before user signs off and accepts the application. then that module is replaced with a temporary program known as driver to facilitate testing. then it is equal to the Expected Value. So black box testers can  perform System Integration testing like this :        Test case 1: Check Balance: Let's say amount is X Deposit amount: Let's say amount is Y Check balance: Expected Value If the Actual Value is X + Y. At this level the modules are sent to the testing department and the test engineers will be validating the functional part of the modules.  l l l         System Level testing :         Arguably. While Integrating the modules they will test whether the interfaces that connect the modules are functionally working or not. then as a whole it can be called as a system (envt. Withdrawal screen & Deposit screen. Automation testing. the Core of the testing comes in this level. But this is cited as vice versa.     l    Top down Approach: In this approach the parent modules are developed first and then the corresponding child modules will be developed. And because EV = AV. the corresponding features need to be tested functionally by the black box testers or Senior testers in the project.     Hybrid or Sandwich approach: In this approach both the TD & BU approaches will be mixed due to several reasons. the developers opt to integrate the modules in the following methods.    Integration level testing: At this level the developers will be developing the interfaces in order to integrate the tested modules.  because depending on the requirement and afford-ability of the company. While integrating the modules in this way. Its a major phase in this testing level. In case while integrating the modules if any mandatory module is missing then that is replaced with a temporary program called stub. link checking etc. which were lengthy and manual. But as the  applications are becoming more and more complex. with the modules as follows. Static means testing where No actions are performed on the application.       The following types are the most is use and we will discuss about each of them one by one. performance & stress testing etc will be carried out in this phase which demands additional skills from a tester. to facilitate testing. + Application)         At SLS level.   User Acceptance Level Testing:     At this level the user will be invited and in his presence.   System Integration Test:  In this type of testing one will perform some actions on the modules  that were integrated by the developers in the previous phase.    .  Assuming that these 4 modules were integrated by the  developers. and simultaneously check whether the reflections are proper in the related connected modules.

In this case one needs to test the field with all possible combinations and different sets of data to conclude that the password field is working fine. If you go by the simple definition of exploring. as per the requirement the testers will check wether the defect is fixed. If the testing is carried out at the client's environment and is carried out by the end users or third party test experts. Remember it is different from stress testing or load testing. & Logout. ( Remember that both these types are before the actual implementation of the software in the clients environment. In this type of testing we are checking the user manual and not the  product. and  released for testing. Logout.                         Scenario 3 : Login. you will also check the  look and feel overall.    Retesting : Its a type of testing in which one will perform testing on the same functionality again and again with multiple sets of data in order to come to a conclusion whether its working fine or not. the installation/setup guide and not the application's capability to install. ( i. then it is referred as Alpha testing. Navigation of the application must be easy to follow. hence the term user acceptance.    Exploratory Testing : Its a type of testing in which domain experts ( knowledge of business & functions) will perform testing on the application without having the knowledge of requirements just by parallely exploring the functionality. abc123.     Example 5 : Lets take a bank application and consider the different end to end scenarios that exist within the application. )   Installation Testing : Its a type of testing in which one will install the application into the environment by following the guidelines given in the Deployment document / Installation guide.    Monkey Testing : Its a type of testing in which Abnormal actions are performed intentionally on the application in order to check the stability of the application.  Scenario 1 : Login. In this case also all the features except the new functionality comes under Regression testing. then it is known as Beta testing . If the customer visits the company and the comapny's own test engineers perform testing in their own premises.  One main point is to ensure that. Which means performing various operations on the applications like different users in real time scenario. one needs to test whether information about all the features are understandable easily.                          Scenario 2 : Login. Withdrawal.  & then doing something related to it in order to know something more  about it. otherwise report the problems in the deployment document. We are concentrating on the stability of the features and functionality in the case of extreme possibilities of actions performed on the application by different kind of users. Deposit. Once the next build is released.  Once the bike is returned to you with new tyres. The test engineers may need to check additionally all the related features of the newly added feature. 56df etc) data and no special characters  ( *. Balance enquiry .Regression Testing : I t s a t y p e o f t e s t i n g i n o n e w i l l p e r f o r m t e s t i n g o n t h e a l r e a d y t e s t e d functionality again and again.         Case 2 : Whenever some new feature is added to the application in the middle of development.    Useability Testing : In this kind of testing we will check the user freindliness of the application. Withdrawal & logout. It means having minimum idea about something. If at all the installation is succesful then one will come to a conclusion that the installation guide and the instructions in it are correct and it is appropriate to install the application.$. whether the mileage maintains its expected value and all related features that can be affected by this change. Deposit.     Alpha Testing  & Beta Testing : These are both performed in the User acceptance testing phase.)      Compatibility testing : Its a type of testing in which one will install the application into multiple environments prepared with different combinations or environmental components in order to check whether the application is suitable with those environments or not. etc. Testing the tyre in this case is New testing and all the other features will fall under Regression testing. and check whether the brakes still work as expected.   l         Authentication Testing :  It is a type of testing in which one will try to enter into the application  by entering different combinations of usernames and passwords in order to check whether the application is allowing only the authorized users or not.    Security Testing : Its a type of testing in which one will test whether the application is a secured application or not.    End to End Testing : Its a type of testing in which we perform testing on various end to end scenarios of an application. A black box test engineer will concentrate on the following types of testing. Depending on the complexity of the application. you tested all the other features and you are satisfied with them. Such kind of repeated testing on any feature is called Retesting. As the name suggests regression is revisiting the same functionality of a feature.e.      Case1 : When the test engineers find some defects and report it to the developers. Before sending it back for changing. In order to do the same.# etc). The development team fixes the issue and releases the next build.       Example 3:  Lets say that you wanted a bike with 17" tyres instead of 15" and sent the bike to the  service center for changing it. . and also whether the related features are still working fine which might have been affected while fixing the defect. but it happens in the following two cases. Usually this type of testing is carried out on products rather than projects.      Example 4:  Lets say the customer wants a bank application and the login screen must have  the password field that only accepts alphanumeric (eg. Balance enquiry.

May 2000.  l  Port testing: Its a type of testing in which one will install the application into the clients environment and check whether it is compatible with that environment. ( Under revision ETA 02/25/09)     Quality Center. Quality Manager courses ..       Sub Index :      Environments      Software testing life cycle      Bug life cycle     ISTQB Certification syllabi and papers     Automation testing. This is to maintain  the size of the knol to under 15-20 pages for easy management.VillanovaU. (2001) Managing the testing process.com 3. Jaanssen. admin . ' So In  this type of testing. H.5 Beizer . PerformanceTester Robot. 8. Buwalda. In order to check whether the firewalls are  working fine or not. Van Nostrand Reinhold:Boston 5. L.blogger. (Under revision ETA 02/28/09)     Performance testing      Quicktest proffesional VBScript. whether it is product or project etc . D (1993) Software Inspection. If you are unable to find the knols.png. UTN publishing van Veenendaal.        Mutation testing : Its a type of testing in which one will perform testing on the application or its related factors by doing some changes to the logics or layers of the environment. (2004). The Testing Practitioner. D & Pinkster. Image Analysis_speedo. B. ) and try to  access other higher level of users pages (ex. pp. E. 7. (2000) 'GQM based Inspections' in proceedings of the 11th European software control and metrics conference (ESCOM).l         Direct URL testing : It is a type of testing in which one will enter the direct URL's ( Uniform resource locator) of the secured pages and check whether the application is allowing the access to those areas or not. 89-97. ISTQB6. M. knol for  details)  Any thing from the functionality of a feature to the applications overall route can be tested with  different set of combinations of environment. ETA .Net savvy. March 197.rttsweb. ISTQB3 Gilb.     Adhoc testing : Its a type of testing in which the test engineers will perform testing in their own style after understanding the requirements clearly.)   Soak Testing/Reliability testing : Its a type of testing in which one will perform testing on the application continuosly for long period of time in order to check the stability of the application.4. 2nd edition. (2001) Intergrated Test Design and Automation. One will enter into the application as one level of user ( ex. SDLC image jpg format.NY www. Heartfelt thanks to Mr Suresh Reddy at NRSTT Hyderabad . Addison Wesley Software Testing Courses 100% Online Testing Courses Request More Information Today! www.         Firewall Leakage testing : Firewall term is a very widely misunderstood word and  it generally  means a barrier between two levels. Analysis image url 2. Artech House 6. please click on the author name and visit the knols list published by me. member. R. retreived on 18/12/2008. T & Graham. B (1990) Software Testing Technique. (unpublished draft proofreading due.com 2008 Retreived on 29/12/2008 . (2003) Testng Embedded software. Addison Wesley 9. ' The definition comes from an Old African story where people used to put fire around them while sleeping. My testing mentor. OIW. Van Veenendaal. 2009 Mr Suresh Reddy at NRSTT Hyderabad 4. ISTQB2.6 coupland. ISTQB3.) . 14 Issue 2.com Rational Training Classes FunctionalTester. E. ISTQB1. Munich. E.com. one needs to find what kind of environment is needed to be tested. 2nd edition. in order to prevent red-ants coming near them.com bp2. L. I. ISTQB4. john wiley & sons: New York. 2nd edition. (Refer envt. and van der Zwan.02/09) References 1. )                                                           Continuation :           The remaining Chapters are indexed below and are published on seperate knols. vol. ( Note that in Exploratory testing the domain experts do not have the knowledge of requirements whereas in this case the test engineers have the expected values set. (2003) A practitioners guide to software test design. 10. and Notenboom. ISTQB5 Black. Broekman.com Comments Sign in to write a comment . ( According to the requirements. Addison-Wesley: London Hatton. bp2@blogger. without whose support this article would not have been possible. (1997) 'Reexamining the Fault Density-component Size Connection' in IEEE Software.

In the mean time I want to take ISTQB fundamental exam. 2009 5:38 AM 0 Hats Off!!!!!!!!!! Hi Vinayak. Rajamanickam Antonimuthu Report abusive comment Post reply to this comment ▼ Last edited Jun 13. Since I am new to testing world. so i am going through the Knol and trying to understand the testing process. Can you please give me how should I proceed for the exam as well as to increase my knowledge in testing? Regarding the knowledge in automation.. Thank you Report abusive comment Post reply to this comment ▼ Last edited Jun 13. Please check whether your definition for alpha testing is correct. But I want to learn those tools... But my current understanding is alpha testing will be done by the customer. 2009 7:55 PM -2 Hunter . I liked the way you have explained Testing with simple examples/scenarios...com Thank You ! Report abusive comment Post reply to this comment ▼ May 13.com. 2009 3:48 PM +6 Anonymous Nice Article -Need clarification regarding Alpha testing. 2009 5:13 AM 0 really wonderful information really wonderful information. 2009 11:37 PM 0 michael Great info Well done! This information was much more detailed and simplier than the information I have gotten from Uni..au w: www. Can you please guide me how should I proceed to learn those tools by my own? or which tool I should learn in the beginning which has a good demand also? Please assist me here.au Report abusive comment Post reply to this comment ▼ May 4. You have mentioned that alpha testing will be done by "company's own test engineers ". Regards Hiten Hiten Shah Report abusive comment View/post replies (1) to this comment ▼ Last edited Jun 7.. then I got the chance to come to testing on financial domain which is dealing with US retirement plan..knowledge in testing Hi Vinayak.com. right now I am doing manual.au mmullins207@gmail. I was a S/W engg having 2 yrs of exp. Regards.com. Hunter e: hunter@ewebmarketing. Hats off!!! to you.ewebmarketing. Michael Mullins mmullins207@optusnet. Nice Article. I have just begun my studies for ISTQB Foundation Level exam and this would help me a lot. so I dont have much idea.You have done a great job.

* your way of explanation is very clear and understandable.. really am very proud of you.. Inpsired by this thoughtfull flow of information from you on this topic has made me mesmerised with the idea of taking up a career in this field. Thanks Asha Report abusive comment View/post replies (1) to this comment ▼ Anonymous Last edited Feb 9.Kindly provide the guidelines for candidates interested in domain migration..Perfect collection Vinayak. software development work... this is a perfect collection for testing and related studies Anonymous Report abusive comment Post reply to this comment ▼ Last edited Mar 12. 2009 10:08 AM -2 This was an awsome presentation of valid information!! kudos Hi Vinayak.10 of 15   Older comments »   Show all comments . please keep it up this. what like in yours than others. Thanks for your sharing your view about Testing.5 yrs experiece in QTP and test cycle. as I am a software engineer by profession with 2 plus yr experience would like to know.. P Uday Kumar Report abusive comment Post reply to this comment ▼ Last edited Dec 22..as I currently in working in anthr dimension. from which i Like to move on to testing as I have been provided with this exposure during my career. note: need one more info from you if you have any Material or document about ISTQB please send to my mail ID: aaru... 2008 10:26 PM 0 1 . will be very useful to all.Will anISQTB certicate help help in taking up a career full fledge in testing ? Assuming the certificate is gained.keep it up hi vinayak.. Really is a very good one than whatever i read till now. will ISQTB certified professional with min 1...com Suresh. 2009 2:14 AM +1 Amazing Information Brilliant summary of Software testing . Report abusive comment Post reply to this comment ▼ Last edited Jan 18.. Please keep it up this way.. Hope to see some more articles from you in future. 2009 8:08 AM +2 Good work. what wud he/she need to do to qualify for oppurtunites in Testing.. I guess this would make testing a very fun oriented subject and easy to learn Anonymous Report abusive comment Post reply to this comment ▼ Last edited Mar 2. 2009 11:02 PM 0 suresh sa Thanks for Sharing Information Thanks Vinayak for sharing information! It was really helpful for me to understand the concept of testing.. i thing this is a main objective of any book or guide. Thanks once again..ja@gmail.I have a query to you on this note. help suffice the person to get absorbed in a testing career? Please provide your inputs as it priovide a gud knowledge of steps necessary to be taken. if a person needs to identify with this new field of work area..

Home  |  Terms of Service  |  Privacy Policy  |  Content Policy  |  Help ©2009 Google .

Sign up to vote on this title
UsefulNot useful