Quality Assurance and Project Management:

test case

1

December 14, 2009  10:00 AM

Ten Specialities Required in a Business Technology Analyst



Posted by: Jaideep Khanduja
business analyst, business technical analyst, Development, documentation, process flow, project completion, project governance, project implementation, project installation, project release, requirement analysis, requirement gathering, technical analyst, test case, Test Plan, tester, testing

A clear cut difference is there between a Business Analyst and a Business Technology Analyst. In previous blog I mentioned the essential skills required in a business analyst. Here let us highlight the essential key skills required in a person to become a business technology analyst. Those are as...

September 16, 2009  12:00 PM

Five ways to workout ‘testing effort”



Posted by: Jaideep Khanduja
business rule, business specification, customer requirement, customer specification, development phase, development plan, functional testing, load testing, performance testing, QC, QC head, quality control, software development, software product, Software Project, team size, test case, test effort, Test Plan, tester, testing effort, testing effort estimation, testing phase, testing plan

A new project, a new product development – as a QC head how do you estimate your testing effort? Well, some quick steps for this: 1. Customer requirements: Customer specifications or requirements captured at the time of initial study period would be a quick reference guide for estimating...


July 20, 2009  10:00 AM

Responsibility of a tester – a different perspective



Posted by: Jaideep Khanduja
bugs report, code writing, coding, customer requirement, developer, Development, development team, product quality, project management, QC, quality, quality control, software product, Software Project, software quality, test case, test report, tester, testing report

The 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 13, 2009  10:00 AM

Five phases of Performance Testing



Posted by: Jaideep Khanduja
benchmarking, bottleneck, execution, load modeling, load testing, performance testing, Project Lifecycle, quality control, 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 testing

As 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...


July 6, 2009  10:00 AM

Five stages in a project when Software Tester becomes Quality Analyst



Posted by: Jaideep Khanduja
analysis, customer requirement analysis, functional testing, functionality, load testing, performance testing, product analysis, product functionality, Project Planning, QA, QC, quality analyst, quality assurance, quality control, security testing, software, software build, software document, software documentation, software functionality, software performance, Software tester, software testing, test case, test coverage, test performance, Test Plan, test result, testing process

A software tester evaluates software based on certain parameters. These parameters are set as per product, customer and organization requirements. Testing could be just of functional features or include load, performance and security. For any parameters a tester has to work as quality analyst to...


March 6, 2009  9:42 AM

Why software testing effort estimation is important after functional specifications finalization phase?



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 timeline

If 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...


March 4, 2009  10:03 AM

10 top “Do this if you want blunders!” in Software Development and Software Testing



Posted by: Jaideep Khanduja
business requirements, change management, Code library, Code repository, development plan, implementation plan, organizational goals, product development, project close-out, project documentation, project management, project methodologies, Project Plan, project standards, Quality Goals, requirements analysis, Risk Management, Risk Plan, software development, software development methodologies, software development standards, Software Project, software quality, Software Repository, software testing, SQA, SQC, test case, test case repository, Test Plan, test standards, time to test, top management requirements

1. Quality Goals are meant only for Quality Department: No department other than quality (project management, product development, documentation, general management etc.) has to read, understand and learn about the quality goals of the organization. It is only the responsibility of...


March 2, 2009  9:59 AM

10 golden rules for Requirements Based Testing



Posted by: Jaideep Khanduja
business knowledge, change management, integration testing, software, test case, test case repository, test coverage, test metrics, tester, unit testing

10. Document with complete and clear requirements is as important as oxygen in the air: Requirements based testing is purely based on the requirements specified by the customer or software sponsor during the business requirements study phase. Documentation of all requirements (user...


February 27, 2009  9:54 AM

Software Quality vs Project Quality



Posted by: Jaideep Khanduja
business requirements, customer requirements, fixing of bugs, functional requirements, post implementation phase of project, project close-out, Project Delivery, Project Development, project execution, project implementation, project initiation, project management, project quality, quality measures, quality metrics, quality standards, software delivery, software design, software metrics, software product, Software Project, software quality, software strategy, test case, Test Plan, test results, test scenarios, test strategy

The definition of QUALITY varies in different contexts. On one hand we talk of software quality that means adopting standards and measures to ensure the building of software product that meets all customer requirements (design, interface, business requirements, functional...


1

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: