I want to know about different activities in different of Testing process in a Compnay. Could anyone please tell me or send me a file or Link to know clear ideas about Software Testing Process Compliance.
March 3, 2008 - 5:13pm
Hi, Please post your questions in forums.
April 17, 2009 - 12:21pm
Its a Great Idea!,..nice concept about Software Testing process compliance,.. Its very simple,.Just Browsing in net ,.. You got lot of infomations. Try it
June 19, 2009 - 8:40pm
In our company the testing process is like this
1)we create test plan
2)we create test cases
3)Execute test cases
6)User acceptance testing
Hope this will work out for you too.The economist subscription
November 11, 2009 - 2:46am
Compliance Testing: This determines that a product implementation of a particular Implementation Specification fulfills all mandatory elements as specified and that these elements are operable. Compliance testing may become more stringent over time, especially as a particular Implementation Specification matures.
For example, a more stringent version may test that a product implementation of a particular Implementation Specification fulfills all mandatory and implemented optional elements as specified and that these elements are operable, accurate (to a reasonable level of measure), and that the elements handle all reasonable cases correctly including errors.
NOTE: Compliance testing WILL NOT ensure, or even test, interoperability of software products. However, as the specifications mature the likelihood of interoperability will be higher.
July 16, 2010 - 12:46pm
Some of the methods for testing:
ACCEPTANCE TESTING: Testing to verify a product meets customer specified requirements. A customer usually does this type of testing on a product that is developed externally.
COMPATIBILITY TESTING: Testing to ensure compatibility of an application or Web site with different browsers, OSs, and hardware platforms. Compatibility testing can be performed manually or can be driven by an automated functional or regression test suite.
FUNCTIONAL TESTING: Validating an application or Web site conforms to its specifications and correctly performs all its required functions. This entails a series of tests which perform a feature by feature validation of behavior, using a wide range of normal and erroneous input data. This can involve testing of the product's user interface, APIs, database management, security, installation, networking, etc testing can be performed on an automated or manual basis using black box or white box methodologies.
INTEGRATION TESTING: Testing in which modules are combined and tested as a group. Modules are typically code modules, individual applications, client and server applications on a network, etc. Integration Testing follows unit testing and precedes system testing.
PERFORMANCE TESTING: Performance testing can be applied to understand your application or WWW site's scalability, or to benchmark the performance in an environment of third party products such as servers and middle ware for potential purchase. This sort of testing is particularly useful to identify performance bottlenecks in high use applications. Performance testing generally involves an automated test suite as this allows easy simulation of a variety of normal, peak, and exceptional load conditions.
STRESS TESTING: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. A graceful degradation under load leading to non-catastrophic failure is the desired result. Often Stress Testing is performed using the same process as Performance Testing but employing a very high level of simulated load.
SYSTEM TESTING: 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.
UNIT TESTING: Functional and reliability testing in an Engineering environment. Producing tests for the behavior of components of a product to ensure their correct behavior prior to system integration.
Tom, Quick search for jobs
January 4, 2011 - 9:58am
Im planning to software testing course , could anyone tell me is there any online certification available for software testing.
February 1, 2011 - 12:07pm
We're doing integration, regression, unit and compatibility testing in our company. This is to ensure that all the modules are functioning properly according to the process and specifications.
Application Developer-Millionaire Mind Intensive
December 7, 2010 - 10:11am
Some softwares may take weeks or months to test and others could only take less than a week. It really depends on what software they are going to test. used alloy wheels
December 21, 2010 - 5:11pm
Some softwares may take weeks or months to test and others could only take less than a week. It really depends on what software they are going to test.
I am testing one diagnostic software since 6 months.http://www.micro-tronik.com/autohex_auto_diagnostic_scan_tool_1.html
January 12, 2011 - 7:42am
Software testing could take a few weeks to a couple of months. It usually would depend on how large the software is and its application as well. If you are creating a global software then you will have to test it over different users. Your client in Japan may want some features added or removed so testing it in those conditions will have variable time and so on so forth.
View the discussion thread.