Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange
27

Your boss doesn't want a flat "No" or to hear their request is impractical. They want to reduce the risk of releasing changes to the application. Make your boss choose your priorities, that is one of the roles of a manager. Add scenarios based on team knowledge and work with your boss to rank them by risk. Implement top priority scenarios Go back to ...


20

John Ruberto wrote an article some years ago on Stickyminds entitled, "Is 100% Unit Test Coverage Enough?". The article can be found here: https://www.stickyminds.com/article/100-percent-unit-test-coverage-not-enough In it he presents the argument that there are different kinds of coverage. One could cover 100% of requirements, but that doesn't include ...


10

It's always good to use numbers to make your point- There are N models and sub models of iPhones (for some applications you should also count the phone's network sub-type), each with M available iOS versions and sub versions (this is not entirely accurate, some models and iOS versions don't work together, but never mind that now) Older iOS versions needs ...


6

I think you need to practice. No matter how good someones GitHub account looks, or what they say they've done, listed on their resume, etc, interviewers are going to want to see some practical experience. Yes, not everyone is good with whiteboard exercises or coding in front of others, but it's pretty standard in most tech interviews. If you're ...


6

Mindmap all the high-level features of the application together with business owners. Go over the map with stakeholders (e.g users, developers, managers, and sponsors). Do a risk assessment with some key people, maybe also analyze brittle areas based on defect reports. Write automated happy-path tests for the highest risk features first. Create a test-...


5

The best way to articulate how much you know is to have some prove of your knowledge. If you can write frameworks, then upload some of your frameworks to GitHub or BitBucket. Using that way you can demonstrate not even the entire completed framework but some basic demo-code of how you solve such or another typical test automation problem. Another good way ...


5

Isn't that what pageObjects are in essence: A description of the UI elements on a Page and how you can interact with them. Now when writing tests you often interact with multiple elements in a certain way to achieve a workflow. Now if multiple tests use the same workflow it might make sense to move the combination of workflow-steps also into the pageObjects ...


5

Normal approach should we automate only functional flow not caring about the UI things like font of text, font type of text, color of text, background color, images, different panels on page etc. In short, DO NOT DO THIS. Automating text/fonts/images is a terrible idea because they can change. Does your marketing team (if you have one) have access to ...


4

👍Pros of coding: You can easily integrate your test into CI process You can code any assertion logic you need in your tests You can utilize any library that is suitable for your chosen coding platform You can flexibly manage your test data You can build whatever test report you want 👎Cons of coding: It requires coding skills 👍...


4

In addition to the other answers, one good way to practice the articulation of ideas is to join communities and discuss different points of view. Online, Ministry of Testing is a great place to start. They have a rich discussion board and a Disqu (I always get it wrong spelled). Your favorite frameworks and technologies should have something similar. ...


4

I've spent a fair bit of time working on safety-related software. People die if the software fails, kind of safety. The first thing to note is that we had 100% test coverage of requirements. However that didn't have to be automated, sometimes because it wasn't practical, and sometimes because it wasn't physically possible. No safety-related standard ...


4

You should consider to keep them simple and use any data for analysis during the timebox to see where to explore next. The charter is just a mission to get you started, not a detailed work assignment and reporting tool. I like the format ckenst proposes in his writing exploratory charters: How to Write Exploratory Charters This is based on "A simple ...


3

In addition to some nice feedback you already got: think of and prepare (before you go to the interview) a few interesting problems you have solved and which you can share. That way you might be more confident in telling about it and don't need to have to improvise.


3

The value of this role will depend a lot on how complex or unusual your product is. If your product is reasonably simple to test and doesn't require complex engineering then there may not be a lot of value in having a framework specialist. For example a website and IOT stack have very different test requirements. As someone who is framework specialist what ...


3

Page objects work well in smaller sites where there is little to no re-use of fields because the coupling effect isn't significant enough to cause major issues - there will always be challenges finding a balance between readable tests, DRY, YAGNI, and SOLID. I've found that once the application is large enough it's better to work in terms of input type ...


3

What's the overall execution time? How does the feedback loop look like? Talk On: Accelerate Automation Tests From 3 Hours to 3 Minutes Can be detailed results provided in a few minutes(or even better in seconds without compromising quality) on the overall health of the build to the relevant stakeholders with relevant metrics? I would ask myself these ...


3

It depends what they consider 100%, but my basic answer would be 'no' especially if these are UI level tests. Tests at this level are slow and expensive to write and maintain. It looks like you know this already, but write tests that cover the broad paths through the application/its functionality.


3

You could tackle that from two directions. You could take the bugs and ask the people who opened the bugs how to reproduce them. There is your testcase. You can probably start automating regression tests for these bugs immediately. Or you could just write the test cases yourself based on the documents and SUT you have. Maybe there is a business capability ...


2

Yes. A beginner can also start developing automation framework with proper guidance from the seniors. For Automating a application beginners needs to consider the following things: Select a automation tool that provide easy and better solution for the application. Select what are the test cases that you are going to automate. All the test cases can't be ...


2

Everything is possible with proper learning and practice. Start to automate with a simple test case. Don't lose your hope when your first test gets failed keep on trying. For Automating the AngularJS Application Protractor is the good Choice You need to learn basics of JavaScript before starting to write the code. I have listed few links for you to go ...


2

What about checking if the process is running by using a CustomKeyword ? In your Keyword: @Keyword boolean processIsRunning(String processName) { def sout = new StringBuilder(), serr = new StringBuilder() def cmd = 'tasklist /FI "IMAGENAME eq ' + processName + '"' def proc = cmd.execute() proc.consumeProcessOutput(sout, serr) proc....


2

In a similar case, we went with writing our own very light weight framework. Reasons are: We were not using many of the features of Soap UI, so just to make Restful calls, Soap UI is an overkill The paid version was costly for our need; extending the free version needed Groovy skills - Groovy was not a language our team was familiar with Soap UI projects ...


2

An alternative solution is to use kantu instead of sikuli. It is an open-source project that is similar to sikuli in many ways, but it has OCR already built-in and the ocr quality is better then Tesseract. is it possible at all to copy text ? In kantu, use the OCRExtractRelative command:


2

When i have given this answer to candidates in the past its because i feel they aren't demonstrating enough programming experience. Quite a lot of test automation is done with tools that don't really need programming skills but are more about assembling work flows using a gui. Such as appium and postman in particular. Try to talk about programming ...


2

I would suggest thoroughly preparing with mock interviews. Have someone like friend or family member as a interviewer to practice with.Make it as tough(even bit more) as real interview. And practice.... practice.... and more practice. IMHO, there is no substitute for practice.


2

The term PageObjects has become greatly over-used (including by me). To reset: We have element locators. Sometimes our element locators also have an action (such as click) with them. Some element locators are at the page level but others can be considered to be at fragment, frame, workflow or domain specific grouping levels These locators are then ...


2

There are two aspects which might impact the way how you structure your tests within classes. Readability. You might want to use classes as logical boundaries so that the names of your classes would represent some area the tests inside those classes relate to. If you use the classes just because you have to implement your tests within classes and use them ...


2

Unless you have a clear demand on automated processing I would tend to storing results in Google Sheets. Here are few points for the choice: You can easily manage the data from wherever you are since it is world-wide accessible service (and has the client applications implemented for all the famous platforms) Sheets provide some data analytics tool-set You ...


2

Welcome to managing your manager. I agree with the sentiment that your boss doesn't want to hear a "No". That's not quite verbose enough. But, the answer is almost assuredly a "No". What you need is a way to communicate how and why to limit your test scope. Even if you tested all the permutations of every make-model, screen-size and OS, you will soon see ...


2

TestContext is being initialized automatically by TestNg. You can access it from your test methods which are listed below (for doing that you need to specify the method parameter in its signature): For some details you can refer to this post. And here is my example of using TestConext with running tests programmatically: public class Main { public ...


Only top voted, non community-wiki answers of a minimum length are eligible