Welcome to Software Testing Help!
What is software Testing? A basic to start with:
Software testing is the process used to help identify the correctness, completeness, security, and quality of developed computer software.
Testing is a process of technical investigation, performed on behalf of stakeholders, that is intended to reveal quality-related information about the product with respect to the context in which it is intended to operate.
This includes, but is not limited to, the process of executing a program or application with the intent of finding errors. Quality is not an absolute; it is value to some person. With that in mind, testing can never completely establish the correctness of arbitrary computer software; testing furnishes a criticism or comparison that compares the state and behaviour of the product against a specification. An important point is that software testing should be distinguished from the separate discipline of software quality assurance, which encompasses all business process areas, not just testing.
There are many approaches to software testing, but effective testing of complex products is essentially a process of investigation, not merely a matter of creating and following routine procedure. One definition of testing is “the process of questioning a product in order to evaluate it”, where the “questions” are operations the tester attempts to execute with the product, and the product answers with its behavior in reaction to the probing of the tester.
Although most of the intellectual processes of testing are nearly identical to that of review or inspection, the word testing is connoted to mean the dynamic analysis of the product—putting the product through its paces. The quality of the application can, and normally does, vary widely from system to system but some of the common quality attributes include capability, reliability, efficiency, portability, maintainability, compatibility and usability. A good test is sometimes described as one which reveals an error; however, more recent thinking suggests that a good test is one which reveals information of interest to someone who matters within the project community.
21 comments ↓
Nice to start with software testing
would like to know stub & driver
We will be using stubs abd drivers in intergration testing (bottom up and top down testing)
while we are testing a applciation by intergrating two or modules together, during that if we face any issue so that we are unable to continue testing say top to bottom/bottom to top, during this time you can include drivers/stubs as temprorary program from developers an dcontinue testing.
Once application has been developed completely these drivers and stubs can be removed for system testing
hi everybody. anybody pls send me sample test cases of any application.
what is the difference between smoke test and sanity test???????????
Hello eerybody,
i would like to know about testdata with example
I would like to know about stubs.
This website is a very good collection regarding the testing. I am a fresher searching a job on Testing.
Thanks a lot.
Thanks, this is really a good site. I learned lot of things in this web site.
Hi
This website has a good collection of articles on testing. This informations will be very useful.
Thanks a lot for providing such a good stuff.
I would like to subscribe the latetst news and comments on this forum.
@suman
Test Data–Data that exist b4 the execution of test and/or exist in the database .Test data may change upon execution of Test Cases
Example…
suppose we have an edit box which accept 4 integer only then test data are 1,11,323,4545,454545,0,like that
suppose we are inserting some into text box which enters records to database then in this case test data is getting modified..
Cheers!!!
RahulKuamar
testing is defined as process in which the defects is identify,isolated,subjected for rectification and ensure that the productis defect free in order to provided a good quality to the product and that must satisfy the customer requirements
Nice……!!!!!!!
Stubs and Drivers are dummy modules used in integration testing
Stubs - Stubs are mainly used in Top-Down intergration testing apporach, which is used to replace the low level modules. Stubs usually dont perform any actions. They may just display the meggase that they are called.
Drivers - Drivers are used in Bottom - Up integration testing approach, which will replace high level modules. They usually perform some actions like, calling a low level module or passing a value. These Drivers usually replace High level modules, which are still under development. So these dummy modules will help to drive testing so they are called as drivers.
hii
nicee………………….
Very………………………………..helpful for me
what is Automation Frame Work
Hi……
A test automation framework is a set of assumptions,
concepts, and practices that provide support for automated
software testing. This article describes and demonstrates
five basic frameworks.
There is no hard and fast rule to use a specific Automation
frame work. It all depends on your project needs, here are
some info on the same.
Data Driven approach is suitable for applications that have
limited functionality but large number of variations in
terms of test data.
Functional Framework is suitable for applications that have
variety of functionality but limited variations in terms of
test data.
Hybrid Test Automation Framework is suitable for
applications that have variety of functionality and larger
number of variations in terms of test data.
Record, enhance and play back methodology is suitable to
convert small to medium size manual scripts into equivalent
automation scripts - one to one basis.
Leave a Comment