Zed Attack Proxy from OWASP - https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project
And generally I would advise browsing the site to learn more about security
Metasploit community edition is free - http://www.metasploit.com/about/choose-right-edition/
I am not expert in search engines, but there are many factors that contribute to how search results are displayed. The query is is essentially the starting point, and how the engine parses the query is important. Also some search engines will 'refactor' the query based on natural langauge algorithms. The order of returned results is often dependent on ...
From the question I'm understanding that you are asking if it is okay to allow the default white page with critical information of probably the page and line number of the code where the error occurred to display in the front-end/production environment/user side.
Simplest and most appropriate answer (as per my understanding) is NO.
The reason being this ...
It's certainly possible - that's the way I and many others here became testers.
As Som Ghosh says, you will need to mention in your applications for test positions that you have worked in testing as well as development. I'd suggest you include details of the kind of testing you've done and the scale of the projects that you tested.
I would recommend that ...
4 and 5 on your list don't seem necessary and may actually be counter-productive. Selenium does ...
This question comes up a lot. Here is a possible solution, but it will require some additional development. You could use a customized HTTP proxy that acts as a pass-through filter except when it sees an HTTP 401 response. In the latter case, the proxy would respond with authentication credentials of your choosing.
Here is how you might do it, in steps:
The wording of the question and the answers seem to miss a subtlety in what you're asking. To not break HTTP, you should always return as a 500. You never redirect to an error page (and give a 200 OK if something bad happened).
Now, whether or not you're bubbling up the stack trace, or just giving a simple "something bad happened" - that's another story. ...
There are much better ways to locate the element aside from using XPath, don't focus on XPath too much - this is, generally speaking, the slowest and the least readable way to locate elements.
I would locate the element by the link text instead, example in Protractor/WebDriverJS:
Example in Java:
While this depends heavily on what part/functionality of a web app you want to test, there is a place and time for both.
For example you might have a pop-up for informing the user about a cookie and have him accept (or decline) it.
Typically this pop-up would only show for the first visit, making incognito mode ideal for repeatedly checking the pop-up ...
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 ...
No. If you ask a normal person (i.e. a non geek) they will most likely think that they have done something wrong. You should always try and be as user friendly as possible. Also the stack trace should never be visible in a production system as that is exactly what hackers are looking for.
One thing we used to do was in a test environment was to surface the ...
If this overlapped texts belongs to single element, lets say label, or text field. You can locate that element and use "webElement.Text.Contains("the text you want to validate");" method to validate your expected text.
And if the overlapped texts belongs to different element, you can simply locate that specific element and validate the text of that element.
There are two ways to do it and I recommend you use both in a hybrid approach.
Talk to your developers, ask them to stop changing web elements if possible. testComplete is a record and play tool, like its cousin Selenium IDE, the way testComplete maps its elements is very structure-dependent, which means if there is any slight change in web element ...
Web service testing independently is needed to ensure the API calls working as expected independent of the web page. In this way, we can confirm that the API calls are working as expected irrespective of the web page elements/functions.
There are many points where tester doesn't feel confident about the application. When a tester performs Automation testing there may be many challenges so web service testing is still very important to know what they need to do, rather than doing it first to learn costly lessons later. The trick is to have an automated tool which can shorten the testing of ...
Actually, the question how to test search engines is part of information retrieval (IR) problem. I will list just a few approaches how they can be evaluated/tested.
Traditional IR approach
One way in traditional IR is to prepare test setup, including:
Dataset of indexed pages
Expected result set (included expected ranking) for each query
In my experience, functional testing of websites isn't much different from functional testing of desktop applications.
The places I've found that can be different are:
Getting a clean test environment can be more complicated (it can also be next to impossible for extremely large corporate web applications)
There will be additional security concerns because ...
Add or inject jQuery and jQuery collision to the web-app under test
Actually you should test web application after your WebService testing is done.
Web Service is an architectural pattern that just allows you to invoke the functions remotely using a widely known HTTP protocol standard (unlike some other remote functions invokations approaches). That is why the client (in your case - a web page) is just one of the possible ...
You can try this tools:
Disclaimer: I'm author of the second one :-)
Eugene S, I had a similar problem with testing UI generated by ExtJS library.
The solution I found useful was to create separate classes for more complex visual components. For instance, for data grid components I have created ExtJsDataGrid class that let me pick up a specific cell in the grid, abstracting me from obscure details in Selenium (dynamic ...
In production, our web application shows a friendly message. While manual testing, we set a test flag that allows a stack trace to appear in the browser. When we are penetration testing or stress testing, we surface the HTTP 500.
You asked about quality, but then you asked about performance, so I assume you are specifically interested in performance. The short answer is no. There are tools that will analyze performance while it is running to tell you which parts of the code are the busiest. Those tools will not tell you whether you are using slow algorithms. And a hot spot is ...
Is there any other things I am missing from my list?
You mentioned "Click on all "link" elements, making sure they are valid, e.g. there is no 404." Is that good enough? Shouldn't you check that the links actually go where they are intended to go?
Are you checking for consistency on all the pages? Should they all have the same look & feel?
Are you ...
There are alot of things to consider. First here are some tool links as there are tons.
Various automation companies:
Some brief info on Approaching Automation:
You need to clarify "high-speed processing" in its requirement. This kind of descriptive requirements is what we should avoid when drafting requirements. Talk to your developers or business analysts, ask them "how fast is high-speed?" and "How reliably is reliable".
I found it a bit hard to believe that your server only accepts 5 concurrent client connection ...
Database shared between tests is a common obstacle.
One way ("orthodox") is to insist that unit test should NOT test database (just exercise the tested library), and mock the DB interface.
Another way ("synthetic") is to use real database, even if such test are not strictly a unit test, but low-level integration tests. Then either:
test might interact ...
I would say you need to test app it in both modes if you're worried about caching issue.
Most of the (functional) testing would be in incognito mode (you are testing how application works, not how it's caching data). The application must work for new users (it's even important than working for retention users) if you want to keep them coming back.
Usually, web application testing services follow the approach of covering both the browser modes during web app testing.
Testing in Normal Browser Mode:
This should be tested majorly for regular users in the app
Cache/Cookies are locally stored on a user's machine, so validation is required, that the user does not encounter any issues due to caching