Tag Info

New answers tagged

0

There are probably two parts to this: Testing every condition that triggers launching an email client. I would use a web-based email client for this. Testing the logic that launches email clients. Since there are lots of possible clients, and you can't drive these with a web automation framework, I recommend testing this by hand. If this logic is not ...


0

With web-automation frameworks you cannot test beyond the browser. Tools like Sikuli or Auto-IT can be triggered (with Process.Start() or Exec()) from the test to do an action that needs input from the operating system outside of the browser. In your case I wonder if just checking the button has the correct "mailto:" link would not be enough. The browser ...


1

White Box Testing In The Absence of Functional Requirements Sometimes, lacking requirements, we read the system code to attempt to discern what it was supposed to do, and then write tests based on that knowledge. This can arise when someone is asked to automate tests for a legacy system. There is a place for white box testing, but it is not a substitute ...


1

What I'm getting from your description of problem is that you have a website developed in C# and need to test it. If you're thinking of writing tests, using Selenium, then it shouldn't matter which language your website is developed. You can have a website developed in C# and still use Python/Java code to write Selenium scripts and then test it. This is ...


1

You could, but you shouldn't. You can just create tests in Visual Studio. Just use the Selenium NuGet packages and write the tests in C#. This beats having two development envs, one for the app and one for the tests. Here is an getting started guide: http://automatetheplanet.com/getting-started-webdriver/ Or this older one without the NuGet package, but ...


1

I'd like to add two more points which will be difficult for firms but as this topic is not limited to this (at least in my opinion) two other possibilities. Both can't be done by QA only. 1) Make your code open source. By making the code open source you'll get more reviewers and more feedback on source code and there will be more installations of your ...


1

You mentioned having a handle on testing, but wanting to know more about documentation in limited time scopes. In that case, my advice would be to get into Jira or another bug-tracking software asap. I like to keep a regression testing google doc spreadsheet which I then insert links to relevant bugs in Jira. That way you, fellow testers/devs/PMs, can all ...


0

I would say it comes down to your familiarity with programming in general. Entry level people will use Selenium IDE, Telerik Test Studio, or something like that (record and click). The minute you need something that isn't right out of the box, you are going to need to learn/use programming to make custom steps. This would be exporting Selenium IDE to Java ...


0

I've figured out how to deal with this issue. I used the Visual Event tool to determine that edits to data in the text box triggered the JQuery change event. Next, I learned a bit of JQuery so that I could use it to set the field value and fire the change event. Finally, I replaced my original code with the snippet below. ...


0

I up-voted GKS1's answer because I have used Appium and it's great, once you get it setup. I will also recommend Telerik Test Studio if you have the funding. It currently only supports iOS but Andorid is coming soon. A major benefit is that it uses physical machines rather than the XCode iOS Simulator. I have found minor differences in emulated devices ...


0

Yes, if you are looking for tool similar to Selenium for mobile application testing, then you should go for 'Selendroid' Refer http://selendroid.io/ Selendroid is a test automation framework fully compatible with Selenium, that's why it is called as 'Selenium for Android'. It can be used on emulators and real devices and can be integrated as a node into ...


1

Have you looked at Appium? I haven't used it but I think it's pretty much selenium for native app testing. http://appium.io/


1

Here are few potential problems along with possible workarounds: You're hitting hardware limits, i.e. server doesn't have enough CPU, RAM, Network or Disk IO to handle 20 users. It may be tested via PerfMon plugin Errors are caused by network connection between JMeter and Application Under Test issues. Check Connect and Latency metrics. If points 1 and 2 ...


1

You should be able to use something like: KEYWORDS = "powershell.exe %s %s %s" % (Var1, Var2, Var3) Run Keywords @{KEYWORDS} See the help pages here You could also use the python extensions to generate and execute the command(s).


2

You can capture the server utilization by yourself too either use the Jmeter plugin http://jmeter-plugins.org/wiki/StandardSet/ this will provide you the CPU, Memory, Network I/O etc. utilization of the server and then you can check whether any of these things are creating bottleneck for you. may be you will find that on increasing the number of users ...


0

I think the issue here because your has style="display: none;". In this case, I think you should click on the div first and try it on Select. Below is my code: WebElement divClick = driver.findElement("//div[@class='form_row']/div"); divClick.click(); WebElement dropdown = driver.findElement("//select[@id='dn']"); Select select = new Select(dropdown); ...


1

You have several choices, although none are perfect. In the order I prefer to use them: Database/data manipulation - unless you have a ridiculously complex data structure (been there) or no access to the database in question (been there, too), this is the simplest, safest way to manipulate expiry/deadlines. Setup/configuration manipulation - configure your ...


1

I am going to coin this user246's First Law of Testing: everyone who tests software will eventually need to test something with a deadline. (I'm sure several hundred thousand other testers have coined the same law.) Although the specifics vary from one problem to the next, there are two essential solutions: either change the clock or change the deadline. ...


0

If you are running the tests in a VM, with an offline snapshot of the DB also in a VM, there is no reason not to advance the VM system date/time as necessary. You could even do the same without a VM but with standalone isolated hardware and the actual system date/time. This has the advantage of mimicking the real world situation better than modifying ...


0

You can pass the "now" time into the function which verifies the expiry (and obviously also the function which creates the credentials). The test function calls it with a hard-coded time, and the production function calls it with the actual current time. For example (untested): def credentials_valid(credentials, now): return credentials.expiry > now ...


1

Good you found a bottleneck, now as with all automated test failures you can question, is it the test, the code or the infrastructure. We cannot answer your situation for you. I would advice to have a developer and a server-admin nearby when performing load tests. The server-admin should monitor and configure the infrastructure and when the infrastructure ...


3

I got the same issue when I use Firefox 39 with Selenium 2.45. After that I upgraded to Selenium 2.46 and the issue got resolved. I think that the problem is the Firefox and Selenium version agreement. Note: the default setting will make the Firefox update automatically.


0

I'd go with a database or file system equivalent (such as CSV) for a number of reasons: SQL querying is a lot easier to learn, use, and maintain than regex Updating your baselines for changes is a matter of a simple update statement or file copy You can control what appears in your baselines and output if you pipe all your output to file/database (or if ...


1

IMHO investing in a transition to a standardized results storage in a database will pay off big time in the long run: changes to script output would only require matching changes in the method of normalizing the results before storing them in the DB validating results would become simple comparisons between standard DB field values easy to handle various ...


1

Kate is dead-on with her suggestion about the short version. If you are REALLY pressed for time, these are the steps I take: You want to save your team time and pain, and you do that by focusing on potential issues that are going to be much less costly if we catch them sooner rather than later. I usually start by asking myself "what feature(s), if broken ...


1

Common UI testing tools (Appium and others) will answer most of your requirements except for Video starts Playing This is tricky and can be achieved to some degree depending on the level of confidence you require. The simplest solution is using the UI tool to get a few screenshots spaced in time, than compare them to each other (verifying that they ...


2

Appium would probably fit the bill. It uses the iOS simulator (comes with XCode) to run Selenium tests. For Android it uses the Android SDK (comes with Android Studio).


0

So What are the dependencies to vary the results(I mean it varies from server configuration,like that i need to know what are the dependencies) ? And can we set the server configuration from the Jmeter. You set the target URL. JMeter makes a series of network requests to whatever endpoint you specify. Please let me know is there any option in jmeter ...


1

As always, it depends. If the application developers have been building unit and integration automation that runs with each build, you aren't as far behind as you would be if no low-level automated checks existed. QA is usually in charge of automated GUI checks and may also be in charge of some of the high-level headless automated checks (such as API ...


0

Some pitfalls I encountered by using simple database operations. Some might be applicable for API and SQL. What is the best order to enter data? E.g. I need to enter customer. So I fill a table of zip codes first. What kind of data is available? E.g. I need a valid zip code. Only a third of the table is loaded. Ofcourse mine is not in the table, so I ...


1

Usually developers write unit tests (because unit tests are close to the code developers know well). Automated GUI test use different instrumentation (Selenium?) so need a bit different skillset. Sometimes might be even developed in different language: because GUI tests are inherently slower, it might make sense to use language like Python which allows you ...


3

When is a good time to develop new automated test, and who should be responsible for this? Developing the structure of the automation can begin very early on in the process. Once the requirements are set the objects can start getting built out, be put into classes and a lot of the assertions can be built that way all that remains is ToDos that hook ...


0

GUI features are dependant on underlying DB, Services, Business logic. Before the gui is stabilized you can focus on automating services, db layer. This would help you focus on sub-systems. Also, when you need to do End to End tests, example- GUI - Service - DB level tests it would help reuse those validations. I would recommend GUI automation when the ...


1

The first three things that come to my mind are: Can you get the product owner to test new functionality? As they know what they want (as opposed to what they asked for) Don't have a test plan, have a one page check list that you can print off and tick off, just so you don't forget any major areas of functionality. Start automating simple things, and ...


1

As your building Windows desktop applications have you looked at what MS has to offer? I think their Lab Management tools are designed for these challenges. Combined with TFS build server its should be able to bootstrap an test environments on the fly for each build and test run. And here an article about combining TFS, Lab Management and CodedUI: ...


0

As you're sending emailable-reports while your test is running you're getting FileNotFoundException .Reports get generated only after test execution. EDIT : If you're sending your emailable reports for the test which has already been executed then you will get previous test report as the current test is still running. I have explained about the solution to ...


2

Telerik's Test Studio is also a good tool and will provide you required support and features. You can use this tool for testing Web, Mobile, Desktop (but only WPF) applications. test Complete is also a good tool which will suffice your requirements (advantage is it supports more variety of Desktop applications). Again, cost wise Test Studio is cheaper than ...


0

Depending on your CI tool, you could just have it kick off a PowerShell or Bash script. That script can be made to handle everything you just mentioned. It is not exactly an out-of-the-box solution, but will only take a few hours to setup if you know a bit about scripting and know what command line commands to call in your script. I used to have script that ...


1

It seems to me that having Acceptance Tests is a must have, and possibly testing sessions for bugs...but I'm wondering if the old school type of test plan....really make sense? Acceptance tests are based on a ticket's Acceptance Criteria. A testing session for bugs... I think you mean a smoke test. Which I advice before every deployment, at a minimum. ...


0

I would go the simplest route; do input-output testing. Perform some action and verify the result. If the communication fails, so does your test as the expected result/response will not occur.


0

Personally for me and the company we like using selenium and using Sauce Labs. To be honest it's the best multiple platform tool I have used, so its worth taking a look at.


0

First of all gather all requirement to automate particular application. From all aspect like what is application, test coverage to automate, frequency of test execution, reporting. Then after based on requirement go with tool selection. If your application is completely web based and should be tested on cross browser on different environment then you can ...


5

The short version: Don't sweat on automation or test cases. Chances are you won't get time to build it because there's too much that has to be manually tested now. Instead focus on building light-weight, easy to maintain documentation of the key elements of the software you're testing. The longer version: This is my world. I'm the sole tester in a team of ...


2

Ouch. No, the old school sort of test plan doesn't make much sense in your context. The only reason I can see for doing them is if you had a contractual requirement with a client to deliver them. Will anyone read them except you? (If no - then stop doing them now!) If you re-read them, what do you use them for? To remind you of how to do something (is it ...


0

First, as @Steve Barnes says, you should NEVER run test on production database. If you do, you are asking for problems, and you WILL get them. Second, part of your test should be test of creating user: if you create user via SQL script and not your app functionality, you are not testing that, and you are creating special program which needs to be ...


1

Both Acceptance tests and Integration tests could be either manual or automated. Unit tests make sense ONLY automated, and I assume your developers write unit tests (as they should). Start with manual testing most often used and most recently changed functionality first, where detecting a problems has best value for time invested. But ask your manager for ...


0

If you have RW access to the source: Build your own APIs/Test Harness into a test solution referencing the source code. This will give you a massive amount of benefits including familiarity with the code, additional unit/integration test coverage and ensuring that you're test set up is executing exactly the way that a user's data would be set up. This will ...


4

Here's how I'd approach this situation (the tl;dr version): Analyze your options and give an indication of the risks involved. Your risk analysis should show your preferred option as having the lowest risk (expressed as a relative number, e.g. 1 being the highest risk and 25 the lowest) and state a few of the biggest risk factors for each potential ...


1

Some tests are better run via a test API as they can then test sections of code that may be unreachable or very hard to reach but a test API does not test the database interface so you also need to test with SQL. The most important thing to remember is Never, Ever, run untested code on a live database - you could potentially do an immense amount of damage ...


0

Here is my recommendation in order of preference: API SQL (Avoid and may be used as a stop-gap-measure until API is available) Create user script (takes time and may have false positives) Most applications these days have such APIs and if your application doesn't have these these it may be worth considering in upcoming sprint/releases. In case you need ...



Top 50 recent answers are included