test execution 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

What could be 10 possible test cases to test MS Excel application (NOT writing test cases or creating a template ON MS Excel)?

Hello All

 i am a fresher form  application background . iIwant to know what is the basic process to perform functional testing on embedded software using automated tool.

thanks

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?