test techniques Questions

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.

 

One of the challenges our QA faces is being able to test our application, which abstracts behavior from the SaaS API, such as the SF API, Eloqua API, Google API, etc., and ensuring the applicatino is behaving correctly.  Some SaaS sources have data that changes and we DO need to also verify data.  Since some of the SaaS sources are also not updateable programatically, you can't know if the SUT is in the state you need it.  Thoughts?

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.

My preference would be tools that have record and playback functionality.  There are lots of automated tools for Windows, but only a few for CentOS Linux.

Hi,

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?

i have one application to test. it has caling functionality. its impossible to test application in all avaliable android device. so give me way to teast it. i have also tried amazon cloud services. but it has limited devices.

Suggest few of the most preferred testing tools which are used to test apps based on REST APIs.

I am using selenium ide for finding the locators,here I got a locator 'link=History of *' which works in selenium ide but when I use the same locator in web driver code it fails.

Says " Unable to locate element: {"method":"link text","selector":"History of .*"} ".
Does selenium support regular expressions in its locators?

 

Please help me out in this.

Which tool is the best for Test Management. It must be suitable for any type of software projects and it can be integrated with any third party issue tracking tools[eg. bugzilla etc.,].

[Opensource, Licensed][agile, general]

Pages

StickyMinds is a TechWell community.

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