2,263 reputation
1626
bio website dzieciou.blogspot.com
location Cracow, Poland
age 32
visits member for 2 years, 6 months
seen 22 hours ago

I know why I am a tester. My driving force is my curiosity: I want to know how things work, why they work and why they don't.

Outside of my regular work I am also a contributor to Awaitility project.


Nov
7
revised How to fix 'Access is denied' errors when trying to .quit() Chrome in Selenium WebDriver tests?
Corrected spelling and grammar
Nov
7
suggested suggested edit on How to fix 'Access is denied' errors when trying to .quit() Chrome in Selenium WebDriver tests?
Nov
7
suggested suggested edit on How to fix 'Access is denied' errors when trying to .quit() Chrome in Selenium WebDriver tests?
Nov
7
suggested suggested edit on How to fix 'Access is denied' errors when trying to .quit() Chrome in Selenium WebDriver tests?
Nov
7
revised SafariDriver is not responding after opening a URL
Corrected spelling
Nov
6
comment Where to focus testing? On integration level or unit level?
Joe, good article. I see your point and I agree having requirements and constrains helps narrow down the context. But it is good to know what constrains matter. And your answer lists some good constrains. So, instead of giving definite answers, can't we just teach and learn what questions tester must ask himself when planning tests?
Nov
6
comment Where to focus testing? On integration level or unit level?
I agree. The clue is to understand what things the answer will depend on. Do you want to have quick feedback on any regression made? Unit tests will execute faster. There are hundreds of such factors and it is not possible to list them all in a single answer.
Nov
6
revised Check-box remains checked up after test and impacts another tests
Improved formatting
Nov
6
revised SafariDriver is not responding after opening a URL
Improved formatting
Nov
6
suggested suggested edit on SafariDriver is not responding after opening a URL
Nov
6
suggested suggested edit on Check-box remains checked up after test and impacts another tests
Nov
6
revised Check-box remains checked up after test and impacts another tests
Improved formatting + inserted explanation from comment
Nov
6
revised Alternative for user extensions in Selenium 2 WebDriver w/ jQuery?
Improved title
Nov
6
revised Check-box remains checked up after test and impacts another tests
Improved formatting
Nov
6
suggested suggested edit on Alternative for user extensions in Selenium 2 WebDriver w/ jQuery?
Nov
6
suggested suggested edit on Check-box remains checked up after test and impacts another tests
Nov
6
suggested suggested edit on Check-box remains checked up after test and impacts another tests
Nov
6
comment Where to focus testing? On integration level or unit level?
I see a lot of both questions like this and answers like "well it depends on the context". So, I'm curious how one can learn to select the right thing for his or her context? One things is by try-observe-correct approach. If a bug in integration was discovered in production I may ask myself what wrong have I done. Another approach would be to write simple test plan with focus area and discuss with peers what is missing. How have you learned to define the focus? I don't mean learning precise numbers, I mean selecting areas of focus of testing.
Nov
6
revised Running WebDriver without opening actual browser window
Improved formatting
Nov
6
revised Automated testing in cloud
Corrected spelling and added link