quality management Questions

In traditional waterfall and agile processes we implement a test strategy to set expectations (and receive feedback) on approach for a release (multiple sprints of work) and test summary to capture results of the execution (functionl, security, and performance testing).  

In a a CI/CD model when we have a 2 week sprint and plan to deploy every 2 weeks it seems a bit cumbersome to do a strategy and summary every 2 weeks.  Ideally the summary could be pulled from an automation tool and produced to a dashboard so that should not be too bad.

Is there a different approach to the strategy?  

Are there other quality tollgates (maybe a bad choice of words) that we should consider?

From a quality process audit perspective is there anything else to consider?

Any feedack appreciated.

-Jeff

By Luis Gil - May 3, 20173 Answers

Have you been measuring how many defects you find at unit testing and system testing per KLOC and how much may cost to fix them?

 

I can find some information like:

with code reviews + unit testing one can find up to 70% of the defects.

https://www.iiitd.edu.in/~jalote/papers/2WCSQPaper.pdf

Other studies say that the cost of finding and fixing a defect at unit testing is $428 and at system testing is $1045.

http://www.ppi-int.com/systems-engineering/free%20resources/Software%20Q...

 

Do you know more benchmarks per industry type ?

What is your experience ?

 

Thanks in advance

 

A compay having projects in several programming languages and frameworks, which agnostic testing tools do you know that can be used in all or several of them?

One example is cloc that counts lines of code.

Which others do you know for static analysis, traceability and other common testing tasks ?

As i have worked in Retail Banking domain as a Sr.Test Engineer(6 years),What kind of technical questions be asked in interview?

What is the future of manual Testing in software testing. And if no automation skills a resouces has where should he move now.What are the diffferent options available.

 

It seems that a popular approach to QA automation is a quick start to cover a most critical area with automated tests ASAP and then proceed automating other areas of testing. This second phase requires more dedicated tool(s). So, what features are most important for such a tool so that it could be useful for your web application?

  • Visual baseline: to compare with results of new test runs
  • Smart CSS selectors: to find and interact with CSS elements on a web page
  • Ignore from comparison: selecting areas on a page which should not be checked for differences
  • Clone, parameterize and invoke tests: reuse existing tests for quick creation of new ones, with the same or new parameters (such as start URL, text entries, login credentials etc)
  • CI-friendly: test execution via Jenkins jobs or with the help of any other popular CI tool
  • Codeless/code-based
  • Your own options?

All of us have our own view of what MUST be the proper New Product Development phases. I believe those are:

1. Ideation: Come-up with an idea you think it could be a market winner.

2. Patenting: Evaluate the merit of getting Intellectual Property (IP) protection for your new product idea.

3. Design: Develop non or partially functioning models of your new product idea and start soliciting user feedback.

4. Feasibility Proof: Perform various technical/business studies to determine IF your new product idea is feasible.

5. Development: Develop a product/process to yield a number of fully functioning new product prototypes as if each of them were to be used by the final user/customer.

6. Controlled Field Use Trial: Let potential users use the new product as IF it were purchased by them and generate feedback based on a previously approved protocol.

7. Design-Verification/Validation: Fine-tune new product design/development and complete design verification/validation studies to confirm the new product meets User Requirement Specifications (URSs) per its respective Labeling Claims.

8. Regulatory Filing (if required): Prepare any required documentation and submit it to appropriate Regulatory Authorities for securing their approval to market it.

9. Full Field Use Trial: Repeat above phase 6 but using a comprehensive pool of potential users/customers.

10. Scaling-up: Scale-up your process so your new product could be manufactured in high quality/low cost conditions.

11. Technology-Transfer: Develop documents' list for new product's production in high volume.

12. Process Validation: Validate your process so it produces final product consistently meeting specifications.

13. Manufacturing: Start manufacture and ship product to market.

14. Launch: Launch product and monitor its acceptance by the user.

15. Line Maintenance/ Improvement: Compile, analyze user feedback and continuously improve product.

What is your opinion? Please explain, if you could.

Each QA automation team has its own specific priorities when choosing a test automation tool to facilitate the UI regression testing process. But what approach is more popular: a lightweight solution which is simple and quick grasp (but will not cover all your regression testing scope) or a full-scale test automation framework which can do much more but will require lots of time to create and maintain the test coverage? What would you/your team/your manager(s) choose and why?

Any recommendations?

I've trialled:

  1. Xray
  2. Kanoah
  3. QTest Manager -  this is very similar to HP ALM
  4. JIRA - create a new issue type in it
  5. Hip Test
  6. qTest Scenario
  7. Qmetric
  8. Test Collab
  9. Test Rail
  10. Test Link

My organisation currently uses HP ALM.

Can anyone recommend SQA Forum to join or SQA user group in Boston area?  Office is in Boston.  Interested in following topics: Selenium WebDriver and UFT automated frameworks, agile testing, mobile testing non-apps (browser based websites on mobile devices).

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.