I'm trying to figure out the proper terminology for our dev/test procedure.
1. The main master codebase in bitbucket.
2. Developers make their code changes (bug fixes, feature improvements) and create pull requests/feature branches that contain their code commits. They are not saved directly into master (so not CI). Each jira issue generally has one corresponding pull request.
3. QA uses Jenkins to deploy individual (or sometimes multile) pull requests on top of the master to our test environments (each QAer has their own test server). So, we are able test the addition of just one change at a time. We do full functional testing and any regression testing we think might be relevant.
4. After QA approves the change, we merge the pull request into the master.
I've worked in QA for 23 years and I'm very very happy with the system we're using. Instead of dev giving us a full iterative version to test, we test and add the parts piece by piece. Nothing gets merged untested so we have great control and minimal risk.
I'm pretty sure it's not Continuous Integration as I've read about it. I thought of the term controlled integration since we carefully check every little thing before it gets integrated, and I see that there is such a concept but I'm not sure that we're doing that either. Or are we? Or something else?
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?
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.
I am a test automation specialist and test manager and I am seaching for ideas in which way I have to change my mindset, my knowledge and tool expierience when beeing part of a development team or company for developping digital services and products?
Want to develop a proposal mgmt system to colloborate and create..what softwares are your choices? the system should serve as a content repositary and provide manage, organize, format and control versions and retain the history of the users. Also to allow the repurposing of the old content whenever it requires. What all the softwares need to be used and approximate timeline to develop a system with a team size of 3?