What are
/r/QualityAssurance's
favorite Products & Services?
From 3.5 billion Reddit comments
The most popular Products mentioned in /r/QualityAssurance:
The most popular Services mentioned in /r/QualityAssurance:
Cypress.io
Appium
TestCafe
Egghead
BrowserStack
TestLink
Charles
Datadog
DEV Community
Fiddler
Sikuli
Treehouse
OWASP Zed Attack Proxy (ZAP)
Cucumber
freeCodeCamp
The most popular reviews in /r/QualityAssurance:
Sounds like it's more overhead than necessary. Why not just something simple and out of the box like http://recordit.co/? I used it all the time in QA and it was great - never got any complaints.
QA not being able to "remember" the steps is laziness and/or incompetence. It's literally their job to find and log bugs. With the use of RecordIt I was able to cut down a lot of time in writing the steps.
I think Appium is the way to go... It's basically Selenium for mobile apps. You'll probably want to look into the Page Object Model design pattern if you've never worked with Selenium before, it'll help you keep things nice and organized.
For Android, you should check out https://github.com/Genymobile/scrcpy - no adapters necessary and performance is quite good. Have used for presenting stuff and remotely controlling my devices. For iOS I won't be able to help but I am sure that similar tools exist.
What he means is you aren't going to find prospective employers on this subreddit. This isn't /r/jobs or /r/freelance or whatever. This is where people who are already employed meet to discuss their work and methodologies.
No one will take you up on your offer here. Anyone desperate enough to take up a random reddit post at face value cannot afford to actually pay you real money.
However, instead of completely trashing your spirits, I will provide an alternative: Apply as a QA tester at Applause.com -- my department has recently reached out to them for support on growing projects. Looks like they're currently hiring, and they're pretty good at what they do. Their testers work from home and I believe have very flexible hours.
Some more info here: http://www.applause.com/testing-services
I don't think your problem is that no one see's the value in manual testing, but it sounds like that's all you can do. It's very important to have a good understanding of manual testing, but most employers are looking for manual testing in addition to automation and other things.
/u/fibbidd gives a good idea for selenium. If you're not interested in one of the many languages that selenium runs on, you could also give CasperJS/PhantomJS (http://casperjs.org/) a try. It will also help increase your javascript knowledge if you're wanting to work on front-end automation.
I think some of the most important things you can probably work on would be:
Test methodology - (ie whitebox/blackbox testing, exploratory testing, pairwise testing, etc.) where/how you would use testing methods like these. Test planning - You should really brush up on this skill, while it doesn't seem very important, many employers I've seen focus pretty heavily on your test planning skills Change management - A lot of times in addition to QA work, employers will be looking to have QA do the change management (ie rollouts, version control, etc). It's good to have a solid understanding of this
If you're really interested in automation, I would suggest picking a language, learning it well enough to be able to write Unit tests/functional tests. I also recommend some type of continuous integration platform, as many employers are looking for people with experience in that area. (think jenkins http://jenkins-ci.org/ )
Our company sometimes has outsourced QA through a company called Applause. Their employees work remotely from all over the world. I don't see any current QA openings but here is a link to their careers page. http://www.applause.com/careers
That's a big topic to learn but I can give you a starting point.
Guru99 is a great resource for learning about testing.
http://www.guru99.com/software-testing.html
I used TutorialsPoint a lot while learning testing:
http://www.tutorialspoint.com/software_testing_dictionary/manual_testing.htm
Both of those sites will throw about 90% of what you need to know at you. Reading is not the same as doing, of course, but at least you'll know the terminology and some of the logic of manual testing.
Google is your friend, and so is YouTube. Go on YouTube and search manual software testing and you'll be rewarded with a lot of good short videos.
Good luck on the final interview! If you are interested in learning automation testing as well, drop me a message.
- TestyOldLady
Only thing I can think of that's similar is oldversion.com:
I don't see excel. You could try a web search for a file extension type. In google if you do filetype:<blah> it will search just for that file type.
There also appears to be a forum at oldversion.com; perhaps someone has asked a similar question there.
You might want to check the https://portswigger.net/burp. Unfortunately, the community edition lacks the "automated" tools, but you can request the trial of the professional edition for one month.
I think this might be what you want. Allows you to USB connect a phone or multiple. Launches a new window that shows your phone. You can use keyboard and mouse to interface with your phone.
Yes, Test Complete is primarily a UI Functional test automation tool. Supports a wide rang of Desktop application types and browsers. Cloud support, plugins for continuous integration, huge ability to expand.
Yes it is.
But you should be using Charles Proxy because that's the king of proxing on MacOS.
There's a free version, but it quits after 30 minute, and it's a really useful tool for mobile QA so it's worth buying the full version.
A good start would be to read some books. Go on Amazon and search for "testing web applications". I would recommend Testing Computer Software by Cem Kaner as a starting point, and once you have some experience, read "lessons learned in software testing".
I havent read this one, but seems like it could be helpful: https://www.amazon.com/Testing-Applications-Web-Planning-Internet-Based/dp/047139470X/ref=sr_1_9?ie=UTF8&qid=1496264155&sr=8-9&keywords=testing+web+applications
Before you learn selenium, I can recommend Headfirst Java . This will make you comfortable with the basics and it will help you follow the videos better.
Are you just watching the video or trying to implement what the video says? I will recommend getting your hands dirty as you go through the videos.
If you can find a partner who is interested in learning these stuff, it can also do magic. It may be your colleagues or someone from here.
You are on the right track. Just keep yourself motivated by applying my tips.
I like that you asked about collecting data, a good step in the right direction - I love collecting metrics across automation test repos!
Whatever you build, no matter what it is from a quality perspective, hook up every part of your process to publish metrics to a monitoring service like Datadog.
- Measure how many tests there are per feature, per team, per commit, per repository. Measure how long test cases take to run per team ownership, per feature, per entire test suite. Some dev teams write crappy tests, you want to be able to identify them, to know which team to help out.
- Measure who contributes to your tests the most often, so you can reward them and give them kudos later on. This also encourages people to contribute more.
- If you have a CICD pipeline containing 10 steps, be sure to measure how long each step, and parts of each step take as well, to identical bottlenecks of slow running pipelines.
- Measure how many tests are flaky and/or skipped as well, per feature, per team. This is often an indicator of bad quality tests and/or lots of bugs.
- You can track all of these things by enforcing mandatory "@Team" and "@Feature" annotations in test cases. Don't allow people to merge tests without these annotations. Create a validation function that blocks merges to master if tests are missing these annotations.
A few days late to the party, but I put together an article recently about 4 common API errors and how to test them.
The "testing" them part is specifically about Assertible, a tool we built for API testing and monitoring, so that part may not be super useful for you (although I'd love to hear your feedback!) -- but the actual errors mentioned in the article are relevant.
Hope this helps! - Cody Reichert
Their docs are seriously great, there's a bunch of info there to help you get started. There are also tutorials created which can be found here: https://docs.cypress.io/examples/examples/tutorials.html
If you're an egghead member there's a course here: https://egghead.io/lessons/cypress-course-overview-end-to-end-testing-with-cypress
It's definitely a bit more of a developer's testing tool than other common e2e automation frameworks, but since you already have a programming background I imagine you can pick things up pretty quickly! You can get started really quick and do some powerful things with little effort.
If you got $20, get a month sub to this: https://egghead.io/series/learn-protractor-testing-for-angularjs -- tutorial with steps by steps on UI automation. protractor framework is hot right now and very easily implemented.
If you don't mind a bit of a homebrew option, we use an AMI for redash hosted on AWS EC2. We set up a basic schema in RDS for storing test results and redash allows us to build charts based around SQL queries pretty easily. Auth is configured using Google Oauth, so anyone with an email configured for our work domain can view or create dashboards. We followed this guide for setup:
Cypress has good documentation, blog posts, and even videos. I suggest that you start there.
They also recommend not to use the page model: https://www.cypress.io/blog/2019/01/03/stop-using-page-objects-and-start-using-app-actions/
We're in the process of switching to Sonarqube (https://www.sonarqube.org/) for our C# projects since it's free and gives some useful information on things like code coverage, smells, and vulnerabilities. You can also tweak the built-in definitions to customize them for your needs. We've set up jobs in Jenkins that run the task as part of our CI pipeline. Hope this helps!
Fiddler also supports simulating slower networks, but it may be overkill for your setup. But it's a great testing tool overall, especially if you're doing a lot of web application testing via a browser.
Have you tried recording what they do with a video camera or some sort of screen recording tool? This has been very useful for me in bug reporting, I imagine it might translate into what you need as well. I'm a pretty big fan of BB Test Assistant and Wink as far as recording tools go.
QA manager here.
I recommend starting with "leading quality" by Ronald Cummings-John, it's short, to the point.
For pure management, anything about nurturing soft skills. I recommend this book https://www.amazon.com/30-Day-Leadership-Playbook-Becoming-ebook/dp/B08GJB1PML?ref_=d6k_applink_bb_marketplace
Good luck
I'd reccommend to read this:
https://www.amazon.com/Web-Application-Hackers-Handbook-Exploiting/dp/1118026470
Pdf available online.
It's not meant for QAs directly but I think that it's very important skill to understand how things work and to be able to find the root cause of bugs.
>I was wondering what specific languages (for coding), automation tools, or any other skills I should focus in on?
If you are new to coding, I'll recommend Java to start with. For beginners , this book helps a lot to get around the basics.
Considering Automation tools, you can start with Selenium. It is a browser automation tool.
>I currently work with mobile iOS and I would really love to improve my skillset, but I have trouble knowing if im on the right path
iOS has a native framework for UI Test Automation. You can invest time on this, if you want to be specialised on it.
As a general note, I would suggest you to get fairly comfortable with one of the popular languages (Java, Python etc.) first and then explore the automation tools. Because at the end of the day, if you don't have good knowledge in the language, it will be tough to read and write code.
You are on the right path, now you just need to start learning. There is hell lot of resources out there in the internet to help you. All the best.
I've been a QA dept lead for 2 years before moving to project management. Here are the basics every manager needs to learn. This is also useful for a team lead, because they also manage people, although not all of them do it well:
- The basics of people management: delegation, motivation and control. What it means, why it's necessary, how to use it.
- SMART task assigning (it's a well-known abbreviation)
- How to give feedback to people: types of feedback, when and how to provide it to your employees.
- How to hire employees. Because you'll need to pick the best for your team.
- And you'll also need to learn about QA management: how to organize the workflow, what skills are needed & etc.
Books for a start that we use in our company to train managers:
- Leadership: The Power of Emotional Intelligence / by Daniel Goleman
- The Goal: A Process of Ongoing Improvement / by E.M. Goldratt
- The 7 Habits of Highly Effective People / by Stephen Covey
- Why Motivating People Doesn't Work . . . and What Does: The New Science of Leading, Energizing, and Engaging / by Susal Fowler
- Hug your people / by Jack Mitchell
read the qa bible, foundations of software testing
Yes, Using meetup.com. There are some software testing meetups, but more often you'll ones for specific programming languages. Don't be afraid to go to a basic JavaScript or Python meetup. It's ok for the topics to go over your head. You're there to talk to people and see if anyone is looking to fill a QA position.
>wrongwaydownaonewayOriginal Poster1 point · 1 day agoThank you. Sounds like a great goal and it's all helping me paint a better picture. I have to study more fundamentals first but thanks for helping me clarify the field a bit.
Thank you! The concept of networking and meetups is pretty new to me (previous field didn't require it), so forgive me if this is dumb: do you mean like using meetup.com? What types of groups should I search for? Thank you so much!
To all the valuable materials other people mentioned - I can add a book: Hands-On Mobile App Testing: A Guide for Mobile Testers and Anyone Involved in the Mobile App Business
I would check out The Complete Software Tester. It provides a lot of knowledge and insight you typically don't get from courses. I think it's a good read for someone new. Plus, you can probably get it for free with a kindle unlimited trial.
What u/i_i_v_o said. I just Upvoted his post. Plus...
Invest in a beginner's book like Becoming a Software Tester by Roman Savenkov
And whatever you do, DON'T PANIC! Your employer knows your pivoting careers, so you should hopefully have at least a couple quarters before performance reviews get nitpicky about skillsets [if at all]. Plus, you've got a friend at the office for support/guidance. You're starting from zero, so there no chance of any perceived "under-performance." Just learn as much as you can, but start small. When it comes to implementing/producing, especially in "undiscovered country," under-promise so that you can over-deliver.
Good luck, and keep us all posted! We're all here to help. :)
Let's connect! I often visit QA Conferences with speeches - such as the following one:
https://www.slideshare.net/IgorVayner/igor-vayner-tdd-teams-dont-need-qa
That's definitely something we want to change! Could you share our questions to your coworker? https://airtable.com/shr4GAG6AU6t4VtIc It really takes 2 minutes to fill in and would really help us
It should be easy to replace. If you want, I am happy to help set it up with you via a video call https://calendly.com/jperl/30min, or you can DM me your website URL and I'll take a look.
In terms of support, we aim to respond to issues within a few hours and ideally have a fix within 24 hours.
I found this book really useful. This is the Java edition, but there's a C# one too.
Design Patterns for High-Quality Automated Tests: Clean Code for Bulletproof Tests by Anton Angelov
It isn't automation specific but you might want to check out Uncle Bob's books. Robert Martins Clean Code Agile Software Craftmanship https://www.amazon.com/dp/B08X2T3DCZ/ref=cm_sw_r_apan_glt_fabc_S6CC21BY0BXCG8FN93FJ
No maps per se but you can list all matching jobs across metro areas on some of the job search boards. Dice.com used to make it very easy to do but it seems that they've changed their search up a bit, I can't get it to list all metro areas by query anymore. You used to be able to do something like this and have it show the number of hits across all major metro areas. Too bad, that was a useful feature IMO.
Here's the same search for Indeed.
NOTE: that's a very broad query, you'll probably want to tweak it a bit. I usually start out with a generic search like that just to make sure I don't miss anything.
LinkedIn's search offers similar functionality but it looks like you need to manually add metro areas one at a time.
It's a shame about Dice, I used to use the all-metro search to do a job market comparison.
I have received the same email notification, and submitted a story to Slashdot:
http://slashdot.org/submission/3969603/browserstack-compromised
I'd suggest you up-vote the Slashdot story (+) if you have received the email and you ARE a BrowserStack customer. Please note, however, that at this stage nothing has been officially confirmed.
Common depends a lot on which domain/area you're more involved in.
- FAANG, SF based, and ML/AI based companies will certainly ask you a coding challenge (typical question from leetcode.com).
- Be prepared to answer SDLC related questions. Apply your answers to real world problems, in terms of using JIRA, CI/CD, Automation, Definition of done, etc.
- You'll often be given some kind of product (the company's product), and be asked on your approach to test/automate it. If the company offers a Demo version of their product, it's very productive to download it and try it out as prep for your interview. Using their product lets you contextualize your answers to the types of problems their company might encounter.
If you don’t want to use Cypress’s dashboard service, you can use the Mochawesome reporter in your CI/CD tool to generate decent-looking reports with pass/fail statistics and stack traces for failed tests. Here’s a good tutorial: https://tsh.io/blog/cypress-and-mochawesome-reporting/
And here’s another: https://dev.to/bushraalam/using-mochawesome-reporter-with-cypress-54pf
Yes, the link that the other person posted contains a lot of useful information. Your devs should be doing some component based testing to validate their frontend components work: https://angular.io/guide/testing-components-basics. To do that component based testing, they're likely using selenium which means that they also need a good locator strategy.
I think you got a lot of ideas in the comment.
I'll leave another one, from Gitlab KPI's I find them really business oriented, and some of them may not make sense for you, but will give you some ideas.
Here are two that I found helpful:
A Friendly Introduction to Software Testing
Reduce Risk and Increase Confidence with Exploratory Testing
I want to pass on a tip. For gaining cheap access to ISTQB training books check out scribd.
I didn't want to invest too much money into the exam prep books. Service is like $10 a month.
I am currently reading this book: https://www.scribd.com/book/264122347/Software-Testing-Foundations-4th-Edition-A-Study-Guide-for-the-Certified-Tester-Exam
Other items:
- there's a newish /r/SoftwareTestingViews/
- http://www.getzephyr.com/insights is pretty decent
- The Flipboard page curated by Zephyr Insights is pretty decent too
I'm in the same boat and this sounds like my reality.
One thing I've found that I've had success with is implementing a contract acceptance phase of the project. I am working with websites, so I'm using usersnap.com to capture client feedback directly (but I'm sure something similar can be done with apps).
I think trying to get in very early on a project will help you to figure out where and how you get involved in each project. I have to lean on my dev team a lot, and they usually make the right decisions.
Totally agree with this. Sounds like you're trying to learn to program at the same time as you're trying to learn Capybara. Take a few steps back and build a stronger base around writing and reading ruby, then layer the Capybara specific stuff on top of that.
I haven't played with it, but I've heard good things about http://exercism.io/ to get actual experience, not just reading tutorials
A good penetration engineer usually have 5-10+ years within development, IT Security & IT architecture etc before even being considered for the role to carry out the tests to be trusted.
We are looking at reviewing design for security flaws, analyse 3rd party libraries for known security flaws and then actual penetration testing with SQL and JavaScript injection, CORS, DDOS or buffer flow attacks.. The list can be made very long. In bigger organisations (I contract for Banks and insurance companies) we do security testing as part of Functional and Integrations Tests but we always take in a third party firm to perform Pen Testing which they are specialized in.
​
OWASP is of course a good start and you got the Kali Linux distro with a lot of open source penetration tools (https://www.kali.org/) to help you with some of the tests but its pretty complex to use.
I'd suggest Greenshot for all your screenshot taking needs. One of the first tools I install on any machine I work on. The mac version isn't free like the windows version and has less features, but I still think it's 110% worth it.
Sad to hear, sorry about that. We're a larger company (maybe ~1000 software engineers) and fortunate to not have to worry much about infra costs much.
Without knowing much context of your company or throwing too much money at the problem, how about possibly renting out an AWS EC2 instance and run these tests on schedule there? The `t2.medium` instances have 2 Core/4GB of RAM and cost like $33/month to run 24/7. If you have an extremely light test suite, the cheapest one is a 1core/1GB ram for like $8/mo. Datadog offers pretty cheap pricing for light metrics usage (dollars per month), but that still adds cost...
Or a joke but not really, maybe turn off your screensaver and power settings and just schedule the tests to run on your work computer in the background :D
TestLodge Test Case Management is what I've used. Solid product, good support, and simple to use. If you need to make a move from Excel to a more organized yet simple solution, this is for you: http://www.testlodge.com/
Yeah, it was like that when I was there. The speed of the emulated devices was not great. It looks like they do offer it now, but it's maybe in another tier of service? https://saucelabs.com/devices
Saucelabs did not have audio support when I was there. I submitted a feature request and never heard back. It looks like people are still asking for it. https://saucelabs.ideas.aha.io/ideas/SLIDEA-I-229
Verify that the schema is the same
https://assertible.com/blog/testing-and-validating-api-responses-with-json-schema
If your team is agile, you could consider Axosoft
For Jira, Agile is a separate module requiring additional licensing fees, though still may be more cost effective depending on your needs.
I was involved in setup/admin for my previous company several years ago, when Axosoft promoted the product as OnTime, and I felt it was far more intuitive than Jira's admin.
It's another name in the hat at least!
Good luck and let us know how your research goes.
Excel would be a great tool for it if you are not using any other test management tools already.
Divide the application into features and sub features. You can dedicate one sheet per feature and list down all of the sub features inside that sheet. Also track the automation status in the sheet as a seperate column.
You can add a column to track the automation as well.
There are some freely available test management tools like Testlink . Just try them out to see that it suits your need or not.
I use this with my team. We love it. You can manage requirements and test plans, can link requirements directly to test cases to show where your validation holds up, and it has APIs to plug into automated test tools. It’s PHP and open source so you can make changes if you want.
its kualitee. Its a an end to end test management tool that supports both automated and manual testing. It offers a powerful dashboard, stress-free project management, requirement planning, test case management, defect management, automated testing, mobile app test management, APIs, No software hassles, laser focus visibility, flexible user control, multiple access mediums, formats, test cycles, enhanced security, email notifications, and user-friendly interface. In addition to this, it provides seamless integration with Jira, Selenium, Bitbucket and Jenkins. This all enables you to perform your test successfully without any failures.
TestCafe: https://testcafe.devexpress.com/ And also it's newer version TestCafe Studio is coming soon: https://devexpress.github.io/testcafe/faq/#what-is-the-difference-between-a-paid-and-an-open-source-testcafe-version
Take a look at TestCafe. It's a free node.js tool for automating web tests: https://devexpress.github.io/testcafe/
1 minute to install and start (some JS knowledge required). Doesn't use WebDriver or Selenium.
You can take a look at TestCafe tests, they have some examples here: https://github.com/DevExpress/testcafe/tree/master/docs/articles/documentation/recipes
They're related to the product, but show general patterns.
E.g. this PageModel test building pattern: https://devexpress.github.io/testcafe/documentation/recipes/using-page-model.html
Check out this article:
https://appiumpro.com/editions/29
Here's some Appium documentation behind it:
Ah the old buzzword soup, where companies have a dozen different terms for the same exact thing.
In Appium we set the geo location for our devices/sims and then test if certain features in the app are functional. If I had to guess it'd be something like that:
http://appium.io/docs/en/commands/session/geolocation/set-geolocation/
You'll need to set up ruby, python or java etc. Appium has a pretty good tutorial that is a little out of date. As stated there are quite a few tutorials and answered questions out there.
If you're looking to automate or make your testing easier, I'd recommend Selenium: http://www.seleniumhq.org/download/
Specifically, appium for mobile website testing: http://appium.io/
Source: I'm an automation engineer for mobile websites. I like using Selenium.
Hello!
I just recently entered QA, but since I'm not seeing any other suggestions yet I wanted to put https://www.browserstack.com/ out there. I could be way off but I picked it up and I'm not that tech savvy (yet). ;)
Maybe look into the other systems already in use at your company and see what QA testing tools they integrate well with. For instance, we use many of the Atlassian products which have some keen integrations with various testing options.
Again, I'm a newbie. I'd welcome feedback on this from someone with more experience too.
We use Browserstack at our place, it's not the best and can be pretty slow/buggy at times but for us it means we get access to a wide range of devices remotely.
I personally just use it for browser testing but I know they do have app testing capabilities on there too.
Which cloud service are you using? I think as long as there is CLI support, which it looks like Cypress has, I believe it can be deployed and executed anywhere (CI or cloud). Browserstack has a doc that seems simple enough:
I'm doing a quick comparison between Browserstack (price) and Amazon AWS (price), and I gotta say, Amazon's offering is somewhat confusing (and probably more expensive!).
*I might be wrong though since I didn't dive in yet to the specifics.)
​
Reading through Browserstack site, it says:
- 2000+ real mobile and tablet devices
So that's $199 monthly for a single user. Hurm ... don't think that's bad.
But I know some business folks would think that a service that costs them "$1" can make the company go bankrupt ...
​
Did you face any obstacles or complexities e.g.:
- slow response time from the devices
- usability test not really suitable for this strategy
- automation not running properly
​
​
You need to set up the project on CircleCI. Your code must be in GitHub or Bitbucket so you can connect the repo to your CircleCI account.
Please read the CircleCI docs, it explains how to do this: https://circleci.com/docs/2.0/getting-started/#section=getting-started
I tried a lot of different selenium implementations out a few years ago. Really wanted to like NightwatchJS but it wasn't very good (could have improved since then). I ended up going with Python because it just made more sense to me than Javascript. But we tend to have Python Back Ends so it made sense.
If you're on a node app, I would look at Webdriver.io or Puppeteer if you're more concerned with functionality than compatibility.
I've been using Cypress to great effect for API tests. It does depend a bit on your API. I think Cypress is best at working with JSON APIs.
I just stumbled on this blog post, and the cy-spok plugin looks really promising for API tests. It's a more readable version of what I am doing with my tests. I'm going to play around with it this week!
https://www.cypress.io/blog/2019/12/23/asserting-network-calls-from-cypress-tests/
I find working within the test runner makes writing API tests, inspecting network responses, debugging tests, etc really easy. I'd advocate timeboxing for exploration of any new tool. Spend 1-2 days writing a couple of hello world API tests and compare ease of writing, speed of test execution, ease of debugging, etc.
Consider your CI pipeline.
Will it be faster/easier to run API tests as part of your integration tests? Do they need to run separately or in a different part of your pipeline? I can run my API and Integration tests at the same time in my CI pipeline, but needs vary. Your team may want to fail builds earlier if API tests fail, or fail builds for API tests, but not integration, etc.
Make a list of pros and cons based on your research, open a draft PR, and share your exploration!
In my opinion - learn Cypress, and get good with it. It is a very desired skill to have that employers are seeking out. Selenium is just too outdated and flaky.
Hello there. If I understood correctly your sign up form is inside an iframe.
Working with iframes is not very easy in cypress, but you can read this https://www.cypress.io/blog/2020/02/12/working-with-iframes-in-cypress/
I hope that helps you.
My recommendation is that you visit the page in the iframe src and test it as it was not an iframe, it should be easier and the outcome is most likely the same.
As for the second question I didn't really understand it. Can you please elaborate?
https://www.cypress.io/how-it-works
Cypress popped in my mind as I read this. It's an easy to set-up end to end testing tool. It's not always ideal since it only functions on Chrome, thus not really doing a well covering test for web applications. But for something like content comparisons it should function fine.
No. It is useful for Cypress too especially if you want to keep your tests atomic and maybe refactor application model code instead.
https://www.cypress.io/blog/2019/01/03/stop-using-page-objects-and-start-using-app-actions/
In my opinion it makes the most sense to write your automation tests in the same language as your application when possible.
Fortunately, there are a lot of nodejs frameworks that are really easy to get started with, have a look at
or
To write tests you probably want to learn a bit of basic javascript, and then maybe take a course on one of the above, or just play around with it (If its your first time, I'd probably recommend nightwatch)
I've used WebdriverIO and CodeceptJS it's not the testng syntax that I'm criticizing. You can use any automation API to write without much difficulty.
What I love is the test runner that takes DOM snapshots which makes debugging easier, and built-in stubbing support.
I a firm believer of using the right tool for the job and if I had to automate IE or mobile devices I wouldn't use Cypress, but if it's just chrome then I would do an analysis of alternatives at your company.
I wouldn't agree with anyone saying that it's a selenium killer since every tool has trade-offs.
Without a source I would challenge your assertion that "very little people seem to understand that selenium is an API and Cypress is a framework" https://www.cypress.io/how-it-works makes it clear that it's a batteries includes solution
I do think their popularity is due to better marketing, but I also think developers like it more so people talk about it a bit at tech conferences.
Do you use a cloud-based selenium grid? Getting the Microsoft browsers working was challenging
Test cafe also seems interesting.
Definitely agree with that. I wrote about how difficult basic visual regression testing can be even though it should seem like a simple thing to do.
Zap is a excellent tool for that and is technology agnostic: https://www.zaproxy.org/
Each exploit is enough detailed to correct by yourself.
Last advice : zap really breaks your app, use it on an isolated (local, alpha, ...) version.
Overall a very solid checklist for each category, nice article!
Re: Tooling/Code Quality: There are also run-time analysis tools like OWASP ZAP that scans running instances of your APIs, apps, etc. In my previous company, we had light-weight microservices, and we were able to easily incorporate these scans as part of our CI before merging.
We have this problem in our organization, testing that API calls in native mobile apps fire based on certain calls to action.
To do so we:
- Use CharlesProxy to capture the calls
- Enable the web interface to start recording before the automated test, stop the recording after the test and then download the recorded session in JSON format;
- Test the session for the required acceptance criteria.
If you want to perform manual verification of the calls, you can export from Charles as a CSV from the web interface and then use column filtering to manually eye-ball the calls.
This is my experience with coding interviews, but based on the responses from others here, your experience may vary.
They probably want to test your overall programming ability, and not your proficiency in a specific language. An if-statement is an if-statement no matter the language, but knowing when and where to use them is key.
You should be comfortable coding without the assistance of an IDE, and you should be able to clearly state your thought process while you are coming up with your code. They don't want to just watch you silently writing the code to a solution.
The kinds of questions you might find can be found here:
https://www.hackerrank.com/interview/interview-preparation-kit/warmup/challenges
There's other challenges on the site too, but for QA positions, they usually don't ask about complex algorithms and data structures like they would for a software engineer. Ideally, you should able to solve these problems in around 15 minutes or so.
When it comes down to the day of, if you can't solve it, that's ok (although it's better if you do). They will most likely try to give you hints, and you should talk it out with them of possible solutions that come to mind and why or why not they are a good solution.
One thing I do at my work is to test behaviours and map them to the various test cases. The reason being, irrespective of the change made, a component can interact and affect the system in only , so many ways.
So as long as the behaviours are tested, you should be able to cover most of the bases. In your case, some of the questions I would ask :
- Who interacts with the new character and how
- Mind map the interactions to keep track of it
- And then apply the
>software/game testing (functional testing, ad hoc testing, combinatorial testing, etc) and then list reasonings against adding that character in the game based off results from the test ideas.
I use the free version of miro.com for some of my stuff. I like the mind maps there.
an example : https://miro.com/app/board/o9J_kl6XFcY=/
Hope this helps.
If you're testing an angular app go with Protractor - either in JavaScript or TypeScript. Everything else I'd say Python, C#, or Java.
If you're on Windows, personally I think Fiddler is the superior and more user friendly tool, and it has the same feature to throttle network speeds. Also, Fiddler is free.
You can learn C# on a mac now... Visual studio now is available for Mac
C# is very similar to C++. If you are just learning, it doesn't matter which language you pick.... Java, C++, C#, python... they are all good to learn with.
I've been experimenting with Mailhog for this and it works really well. It's open source so you can self-host it. I've used it to catch emails during testing and easily make any assertions through its API.
The main downside is that you have to run and maintain the service which is an additional moving part, but the service is easy to run so it shouldn't be a big issue.
Depending on web or console based game testing, nothing too out of what I'd assume people are experiencing elsewhere in SQA - lots of Selenium based testing, Sikuli, javascript's still relevant.
Also, from the few AAA's I worked on, it wasn't so uncommon to have us becoming familiar with and work directly within the Unreal Engine - but that was largely just for us to understand map design, trigger areas, and more deeply inform our functional tests.
Lots of opportunities in my town, but I live in a hub city for games and most of the positions are seasonal and low pay.
​
I've tried a couple times to get it up and running and wasn't happy with the results. Haven't revisited it in a year or so though so maybe something has changed for the better. Good luck.
Confluence seems to be the most common solution and we used it for a while but always found it pretty slow and cluttered. The search functionality feels completely broken at scale. Their markup is inspired by Markdown, or probably Wiki, but is just not compatible with true Markdown.
Moved our documentation and knowledge base to Nuclino (https://www.nuclino.com/) since then. The formatting options are a lot more limited but otherwise a much more frictionless experience. Similar hierarchical organization but with faster search.
Don't be scared to get up and go talk to Devs. I've found a lot of times that a simple miscommunication or interpretation of something could have saved a lot of my own time or effort.
Also, I like to build up a mindmap of all the things I want to test on the thing I'm testing. I use a free mindmapping tool called Xmind for this. https://www.xmind.net/
Never stop learning. Grab any opportunity to learn something new in the field.
Good luck!
I have not conducted any QA regarding Bluetooth.
I have played Minecraft on mobile with a controller. SteelSeries Nimbus+ Bluetooth Mobile Controller https://www.amazon.com/dp/B088K6LPG2/ref=cm_sw_r_cp_api_glt_fabc_K4DGF660R4YA7K7Q0Z2C?_encoding=UTF8&psc=1
How to break web software
I recommend it because it does a nice breakdown of approaches and tools to fit various test purposes. Look for the newest edition.
All shiny and Chrome:
Chrome UA Spoofer - for user agent spoofing
Auto Refresh - for keeping a session active in case you are into such stuff
FoxyProxy - a proxy on chrome
Full Page Screen Capture - guess what it does
Web Developer Form Filler - for those long forms that need filling
EditThisCookie - to edit ALL the cookies
hairylunch that's because I believe there is nothing special in our field when it comes to recruitment :)
I linked useful mind map though, and recommended Thinking, Fast and Slow just like Gurock
Hmm...
Agile Testing is a good intro to setting up testing in an agile environment. It lacks actual testing methodology though. Bach and Bolton have a course on rapid software testing,which due to its evolutionary nature (or probably the money made by teaching it ) it doesn't have a textbook. But the blogs /u/rocketbootkid mentioned are written by them.
Ministry of Testing has some good pointers. Rosie does a great job there promoting the community and spirit of this new testing style.
ISTQB if you must but it's like any old hat certification thing. It will teach you how to test in a formal and limited scope and not touch on the creative or bastardry needed to be a good tester. Thing is is that I refuse to discredit it outright because it still has something to teach (or to quote James Bach 'all books teach you something, even if it's not to read that book again'.)
As a side I'd recommend The Intuitionist by Colson Whitehead, The Black Swan by NNT, the art of looking sideways by Alan Fletcher, Peopleware by Timothy Lister and Tom DeMarco... probably a whole host of others. Last one there is worth it though if you think there are problems with your work but cannot fathom what the causes are.
That is how long the classroom course is. It may take you longer to self study but that depends on you so I couldn't estimate. I would say it is worthwhile though. This is the course book.