サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
ニコニコ動画
testing.googleblog.com
Looking forward to getting my hands on Espresso. Would be interested to get your thoughts on appium. ReplyDelete
TotT 98 GTAC 61 James Whittaker 42 Misko Hevery 32 Anthony Vallone 27 Code Health 27 Patrick Copeland 23 Jobs 18 Andrew Trenk 12 C++ 11 Patrik Höglund 8 JavaScript 7 Allen Hutchison 6 George Pirocanac 6 Zhanyong Wan 6 Harry Robinson 5 Java 5 Julian Harty 5 Alberto Savoia 4 Ben Yu 4 Erik Kuefler 4 Philip Zembrod 4 Shyam Seshadri 4 Adam Bender 3 Chrome 3 Dillon Bly 3 John Thomas 3 Lesley Katzen 3 Ma
"Sometimes you can't use a real dependency in a test (e.g. if it's too slow or talks over the network), but there may better options than using mocks" Often the easiest solution is to refactor interfaces. In this case, the PaymentProcessor probably shouldn't be searching so deep into the CreditCardServer's dependencies. One possibility is to create a TransactionCreditCardServer that wraps communic
Very interesting post. I will be looking into implementing something similar in our system. I have one question. If the servers are receiving requests I assume they are running inside a service container. Starting up the likes of Tomcat WebSphere jboss etc US very slow. How do you manage to include these tests in a continuous build environment , they must be slow.? ReplyDelete Hi Dave, Yes, the te
"... the TEST macro (what else would we name it?):" According to Kevlin Henney the word 'case' has significance here too: "A test case corresponds to a single case, it has a single reason to change. Kevlin Henney in "Making Steaks from Sacred Cows", at ca. 0:58, http://vimeo.com/105758303 ReplyDelete
Interesting project, but wouldn't it have been more productive to enhance Selenium with these features rather than reinvent the wheel? Seems like you could have just as easily made a Selenium IDE extension for Chrome with the same issue tracker integration, and the benefit that you could leverage the existing Selenium Grid and Webdriver capabilities. Bit disappointing that instead we end up with t
I can't check out the source code. Every time I run "git clone https://code.google.com/p/script-cover/", I get following output: Initialized empty Git repository in /home/jboss/tmp/script-cover/.git/ fatal: https://code.google.com/p/script-cover//info/refs not found: did you run git update-server-info on the server? I would really like to give this extension a try! ReplyDelete
I like this idea because it looks like it will make developing a rich coverage list fast. And the summary/reporting information you can generate looks useful too. And no long paragraphs are required. Where do you deal with issues like; - what test data will be needed - what test equipment will be needed e.g. mobile handsets, TV's, browser combos - estimates of how long testing will take - what you
@vvk: There is currently no Window support, though it's a possibility in the future. (If you have the expertise to make this happen, please get in touch via the discussion list linked from the project home page.) ReplyDelete
Great article. I don't think I'm alone on this but I'd love to see what google QA uses for test case management...especially if it's an internally developed one. Is there any news about this? ReplyDelete I'd have to say that this article most insightful! I view myself as pragmatic and somewhat of a purist when it comes to testing processes and documentation. This is my take away: For US Federal IT
Post a Comment The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments. TotT 98 GTAC 61 James Whittaker 42 Misko Hevery 32 Anthony Vallone 27 Code Health 27 Patrick Copeland 23 Jobs 18 Andrew Trenk 12 C++ 11 Patrik Höglund 8 JavaScript 7 Allen Hutchison 6 George Pirocanac 6 Zhanyong Wan 6 Harry Robinson 5 Java 5 Julian
This is a great concept, and one that I've had a lot of questions about in my test role in a CI-focused team. Two specific questions: 1) How well does this scale when you have a much more larger and more complicated graph of test (i.e. orders of magnitude)? 2) When running system-level, rather than unit-level tests, can one really map tests to limited domains enough to significantly cut down the t
Yes we all are reading and enjoying every bit of it. Waiting anxiously for upcoming posts. Though as you mentioned tools will be covered in future posts but still what is "Industry leading recording technology" that "converts manual tests to automated tests"? ReplyDelete
Hi, I found CRAP and the video interesting. I wanted to run it on my project and check the amount of CRAP currently in there.But, the links for downloads do not work. I tried to get the Eclipse Plugin. But I get the Repository not found error. -Panna ReplyDelete
Thanks for sharing your experiences. I like the way you do things at google :-) ReplyDelete Hey James, I haven't been in a testing position for very long, but I've been actively scouring the blogs and reading up on different methodologies in my free time to supplement my hands-on experience. The lack of experience may prove my following point to not really be the case in some companies, but I'll m
Interesting. I had never heard of Test Engineer being used as a job title before. Does the addition of the word engineer really represent what the job entails? Or do you think it is a reaction to the typically pejorative title 'tester' or 'QA'. Note: I write test automation code for a living, and have always wondered what a suitable job title should be. ReplyDelete
Thanks for the interesting post. 2 questions about : "So this means that testers report to Eng Prod managers but identify themselves with a product team" 1) does this also apply to developpers ? 2) Where are Eng Prod Managers sitting ? Meaning : are they embeded in projects also or they stay outsite ? Thanks, Laurent ReplyDelete
Small tests should be isolated from each other, but this constraint gets in a way of medium and large tests (especially for web testing). Take a look at what users are doing with Selenium + TestNG. Also, dependencies and high parallelism are not mutually exclusive, it's unfortunate that this rumor is still around. Here is why: http://beust.com/weblog/2009/11/28/hard-core-multicore-with-testng/ Rep
For same reasons I start reviewing a code from headers, rather than implementation. ReplyDelete Interesting, but there is some danger in here as well. You could see Code Review as a different form of testing. Like a view from a different angle on the product. If you first look at the (unit) tests, don't you loose some objectivity as you start to think alike the one that wrote the tests (which is i
TotT 90 GTAC 61 James Whittaker 42 Misko Hevery 32 Anthony Vallone 27 Code Health 23 Patrick Copeland 23 Jobs 18 Andrew Trenk 11 C++ 11 Patrik Höglund 8 JavaScript 7 Allen Hutchison 6 George Pirocanac 6 Zhanyong Wan 6 Harry Robinson 5 Java 5 Julian Harty 5 Alberto Savoia 4 Ben Yu 4 Erik Kuefler 4 Philip Zembrod 4 Shyam Seshadri 4 Adam Bender 3 Chrome 3 John Thomas 3 Lesley Katzen 3 Marc Kaplan 3 M
Wow!!! Truly inspiring... 1(!!!) Code Repository All builds from HEAD... I will have to go through it over and over to get the best out of it!!! I dedicated a post to it in my small little blog. Proud Tester Blog It deserves it. ReplyDelete
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments. TotT 97 GTAC 61 James Whittaker 42 Misko Hevery 32 Anthony Vallone 27 Code Health 26 Patrick Copeland 23 Jobs 18 Andrew Trenk 12 C++ 11 Patrik Höglund 8 JavaScript 7 Allen Hutchison 6 George Pirocanac 6 Zhanyong Wan 6 Harry Robinson 5 Java 5 Julian Harty 5 Alberto
I'm interested in your claim that extending classes from the outside makes for code that is easier to test. I've often heard that the experience from languages where this practice is prevalent (Ruby and JavaScript, specifically) that this makes code harder to understand and sometimes causes unfortunate complications, especially when you mix several libraries that extend core classes in subtly inco
I have seen a Selenium test suite (for a very AJAXy application) that had random unexplainable nondeterministic failures. Actions like "wait for element with id=foobar to appear" and then the immediate next action "click on element with id=foobar" would suddenly say it couldn't find the element any more---but only sometimes and not always. People spent hours trying to find the root cause, without
It is a very nice implementation of a great idea. Thanks for sharing! ReplyDelete Cool stuff! Do you have any information on writing tests against asynchronous APIs? I've made heavy use of jquery events for testing asynchronous calls with ScrewUnit, but I don't see anything here to cover that. I guess if jquery loads you could just use that on top of this. Speaking of ScrewUnit, if you came up wit
Hi I enjoy the blog! HW IP verification has a lot of interesting tools and methodologies such as for instance constrained random testing. Another interesting aspect of this is that it enables metric driven verification since not only line and branch code coverage are measured but also functional and cross functional coverage. Another interesting aspect of this is that there are tools that inserts
Misko, This is a great writeup. I've been looking for a good explanation of why statics almost always lead to "badness". The slow evolution of "simple statics" to "bad statics" is hard for people to spot. It's sort of like a glacier moving. But eventually you blink and take a fresh look and realize a LOT has changed. Thanks! Patrick ReplyDelete You can unit test procedural code. Take a file of fun
I was so waiting for this Post, though the http://www.youtube.com/results?search_query=gtac+2008 had worked great. Thanks Google for this wonderful conference, thanks every one who participated. Thanks Lydia for the post. ReplyDelete
次のページ
このページを最初にブックマークしてみませんか?
『Google Testing Blog』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く