July 20, 2009 10:00 AM
Posted by: Jaideep Khanduja
bugs report,
code writing,
coding,
customer requirement,
developer,
Development,
development team,
product quality,
project management,
QC,
quality,
software product,
Software Project,
software quality,
test case,
test report,
tester,
testing reportThe responsibility of a tester is to ensure the peace of mind of the end users who are going to use the software product. Another target should be to safeguard customer's investment in the product. In order to discharge this responsibility, the tester should focus all his skills on understanding...
July 15, 2009 10:00 AM
Posted by: Jaideep Khanduja
Bug,
bugs report,
business analyst,
development team,
implementation team,
product approval,
project implementation,
project management,
project management framework,
project methodology,
project team,
Q-tag,
QA,
QC,
Quality-tag,
re-testing,
software build,
software implementation,
Software Project,
stakeholder,
team,
test report,
testing,
testing teamIn any software development and implementation company there is always a need of quality assurance and quality control people who own the responsibility of setting the right methodology and framework for development and implementation (QA), bugs identification and product approval (QC). Usually...
July 13, 2009 10:00 AM
Posted by: Jaideep Khanduja
benchmarking,
bottleneck,
execution,
load modeling,
load testing,
performance testing,
Project Lifecycle,
scripting,
Software Project,
software testing,
stress testing,
test case,
test execution,
Test Plan,
test report,
test script,
test strategy,
testing,
testing component,
testing lifecycle,
testing parameter,
testing phase,
testing report,
testing script,
testing tool,
volume testingAs in a software project, the complete project lifecycle comprises of different phases. Similarly the performance testing lifecycle also comprises of various phases. Performance testing is usually, as the name suggests, is done to evaluate or examine the performance of the software product with the...
March 6, 2009 9:42 AM
Posted by: Jaideep Khanduja
bug report,
bug-proofing,
bugs report,
business process,
business rule,
developer,
development team,
functional coverage,
functional specifications,
functional specifications finalization,
quality standards,
sizing of software testing effort,
software development,
software testing,
software testing effort estimation,
test case,
test estimation guidelines,
Test Plan,
test plan guidelines,
test report,
test result,
testcase,
tester,
testing,
testing effort,
testing guidelines,
testing knowledge,
testing plan,
testing time-line,
testing timelineIf we go by quality standards the sizing of software testing effort has to be done before the tester(s) start writing the test cases for the purpose. The estimate will clearly draw out of the functional specifications signed off between the customer and vendor. Without sizing the Testing manager...
