To answer the question "are they worthwhile?", you need to explore:
How expensive (in terms of time and money) are they to create, maintain, and execute?
What value are these tests providing? Are they finding bugs? Providing confidence?
Are there other, less expensive, ways to provide similar value?
I once worked at a software company which built desktop ...
TestStack White: (partial open-source)
White is an open-source framework for automating rich client
applications based on Win32, WinForms, WPF, Silverlight and SWT (Java)
platforms. It is .NET based and does not require the use of any
proprietary scripting languages. Tests/automation programs using White
can be written with whatever .NET language, ...
As of my reading-
Guerrilla Testing means going into a coffee shop or another public place to ask people there about your product or prototype. It can be conducted anywhere ex- cafe, library, train station etc, essentially anywhere where there is significant footfall.
Guerrilla testing works well to quickly validate how effective a design is on its ...
Desktop software usually requires installation. Web applications usually do not.
But web applications are sometimes expected to be running 24x7. This can make upgrades and maintenance more of a challenge to plan and execute (and thus test)
In addition to browser versions mentioned by others here, you may need to worry about browser add-ons
You may also need ...
In case of responsive web application that I'm working for. I use Galen Framework. Galen has their own syntax to define properties of web objects; width, height, position, alignment, text, color and many more.
Its simplify and human-readable syntax works for my non-programming co-worker. and it's work well with Selenium GRID and I also use Jenkins to kick it ...
My experience is that UI automation tools differentiate themselves by the kinds of interfaces they interact with rather than whether they facilitate "basic" testing or complicated testing.
I think you will have a hard time finding a single tool that covers both native applications (what you called "locally installed GUI front-ends") as well as web ...
I do not think the UI testing is very different: field validation, default values, resizing, scalability, and so on.
You probably need to support more than one brand and version of web browser, and perhaps even some mobile devices. You may want to separate your business logic tests from your browser-level tests so that you do not repeat every test on ...
Is it possible to wrap around Selenium 2.0 WebDriver Test Cases with
anything other than NUnit for C# code?
Yes. Extending the user246’s answer, Selenium is just a library that allows you to manipulate with web pages. Unit Test Framework wraps your tests and helps you to run the tests and produce the test execution report with number of passed/failed ...
Answering your question requires knowing why you were asked to write those tests. Unlike solving applied math problems, we usually do not write automated UI tests for the sheer pleasure or the intellectual challenge. I assume you were asked to write them, in that style, for a reason. If there is a reason to believe the UI is particularly buggy and that it ...
Combinatorial explosion of varieties: You may need to test each version of each browser on various hardware running various operating systems
Front-end testing can be easier because of the universality of the displayed information
When you do performance/load testing you're simultaneously testing the machine the server is on, not the current desktop (unless ...
GUI automation is very tricky to say the least. As a general rule of thumb GUI automation demands that the automated test 'know' the machine state at all times. This means that we shouldn't assume that a particular window has focus. If the automation requires a window to have focus it should check to make sure that window has focus and if not set focus to ...
Apart from "what those other guys said", all of it very good advice, some other considerations I'd recommend are:
Usability - Desktop applications tend to have a help file built in, where web applications should be more or less self-explanatory.
Load times - this one is a big pain point. Not everyone has broadband (and we won't go into how much I despise ...
The most efficient tool for testing the appearance of a website is still the human eye and brain.
That said, if you want or need to automate, image comparison is probably the least effective method because even with fuzzy logic it can generate far too many false positives. All it takes is a change in hardware (a different monitor or video card - this will ...
The Microsoft stack is surprisingly still very popular, regardless of other cheaper alternatives.
TFS is basically the central repository. Call it git and Jenkins rolled into one. It manages version control as well as builds.
MTM is just Microsoft's test management tool. This is very useful for linking a manual test that has been created within MTM (its ...
What is Guerrilla Testing:
It is a way to get some quick user feedback on your product or prototype. I can say its usability testing.
Guerrilla Testing Covers:
It covers an activity by which you need to conduct it where your audience are novice users and observe these -
Can they find the content?
Is the language relevant to them?
Have they understood ...
There are number of tools available in the market for Screen capture. You can download from following links.
Gadwin PrintScreen: http://www.gadwin.com/download/
Jing : https://www.techsmith.com/jing.html
As of my reading-
It is nothing but a Protocol testing.
User / Client can apply any techniques to accept the project.
They will apply white box or grey box or black box for accepting the project.
So we are calling the user acceptance testing as a red box testing.
Yellow box Testing:
Yellow box testing is checking against
the warning ...
This is a newer answer to this question, so give the state of things as of Feb 2019... I would say Appium, Microsoft is deprecating their Coded UI Testing tools and suggests using Appium + WinAppDriver.
Coded UI Test for automated UI-driven functional testing is deprecated. Visual Studio 2019 is the last version where Coded UI Test will be ...
According to the Quick start guide the principle method used in generating the test code is CheckView(). Which compares two png screenshots of a screen a before and after then throws an exception if there are any differences. In the background it does this with some unit testing code:
static IcuTest ICU = IcuTestStarter.IcuFromDir(@"c:\test_data");
I am looking for a specific tool which will help me document what I
see when I perform web site usability evaluations. At the end of each
evaluation, I need to create an report for my client.
As your demand above, I would think a tool called qTrace could help you out. It's a complete screen capture tool that helps a tester easily submits clear and ...
I accomplished a similar thing by running the SoapUI tests within the Maven Build
one of the outputs is "junitReport : Turns on creation of JUnit-reports, (true/false)" which will then let you use any of of the million JUnit graphing tools.
Hope that helps in finding your solution
In my last four years as test automation engineer I developed test automation solutions for web applications and mobile applications. For both application types we always decided to automate functional tests.
My opinion is, that no automation tool is good enough to check the GUI well enough. There are so many things you have to check: Colors, position of ...
The prerequisites for starting the object mapping mode are:
project is created and opened
a connection has been made to the AUT Agent (if this is successful, the "Stop AUT Agent" button on the toolbar will be enabled)
an AUT has been configured via the project properties
the AUT has been started. Your AUT is successfully started if the AUT can be seen to be ...
Selenium is an industry standard for web GUI. But desktop GUI automation is almost an untilled field. There are several disparate tools that are able to deal with few types of GUI. I know only one cross-platform open source project for GUI testing based on accessibility technologies (therefore text-based): it's LDTP. But in my mind the interface is really ...
Gorilla Testing is a testing technique in which testers or developers also join to testers to test a particular module thoroughly in all aspects.
Gorilla Testing is a technique in which repetitive Manual Testing process, which a tester would have done several times before, is done again to test the robustness of the system.
Here, one module of the ...
But, you are describing tests that involve user interactions which suggests an end-to-end testing tool. And, there is one that was made specifically for AngularJS applications (even though the app does not have to be AngularJS based for it) - Protractor.
Let me add my options
There are some addons installed or not isntalled in DEV/QA browser
There are networking or routing specific which makes client calls from DEV go to different resources (e.g. hosts file configuration) and that could impact if your UI is built with the help of Ajax requests
There are different locale settings or time settings on client ...
I agree with Aniket, this kind of exhaustive UI test is not worth it. Another thing to consider:
Awhile back, I inherited a manual test case plan from someone who left the company. He had been doing things like checking the list sorting behavior in every area of the app. He wasn't a programmer and didn't understand that the code behind the dropdown box for ...
I would likely just use Word, using a template to contain my questions.
When I purchased a house earlier this year, the Inspector used Word. The resulting book looked exactly like what you are proposing for your final report.