requirements Questions

I have a Project Test Report template but it seems to formal.  I'm looking for ideas for an End of Sprint Test Report, that only reports Manual Regression Testing results.  I need a report that helps me keep track of user stories not ready for regression in one sprint but will be in the next few sprints.

I'm using VSTS Test Hub, so I have access to charts and queries from tests I've run.

Going forward, I would like to report on Automative (and Manual) Regression Test Results.

Appreciate your expertise.  Thanks.

 

 

Provide me Test Case Documents , Which type of Scenarios follow in Registrion Pages?

which type of testing types apply

The Zephyr Api: https://marketplace.atlassian.com/plugins/com.thed.zephyr.zapi/cloud/installation

Power BI: https://powerbi.microsoft.com/en-us/

Has anyone managed to actually integrate the api into Power BI? and if so how did you do it? The jira rest-api has been integrated but vital information based on test cycles is all missing.

 

Is there a free alternative to ZAPI to expose that data as well?

 

Thank you!

how to test vulnerability of ecommerce, whether the applied security is properly working or not?

whether the website can be hacked by anyone or not

Looking to ensure we meet EAL-4 for a product and need looking for the best reference material. Thank you. 

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?

By Lin Sargent - October 26, 20162 Answers

What do you guys think the specifc requirements for 'efficiency testing' would be. The same as those for load testing/response times?

In the Quality Center Requirements module, should we link test cases at the EPIC or story level for traceability and coverage

Pages

StickyMinds is a TechWell community.

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