development lifecycles Questions

Presently I'm a manual tester and completed Selenium course. My area of interest is Gaming. So what are the options are there to move over gaming technology through software automation?

I want to migrate the data from Magento 1.9x to Magento 2.x. Can anyone help me out this?

By Snehal Pailkar - December 8, 20171 Answer

A trend is observed in the IT industry, that the relative weight of testing is dramatically increasing; why?

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.

 

 

I am planning to learn Appium TestNG framework, is it worth to learn ?

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!

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?

Any feedack appreciated.

-Jeff

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

Pages

StickyMinds is a TechWell community.

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