Should tests be in the same Ruby file or in separated Ruby files?
While using Selenium and Ruby to do some functional tests, I am worried with the performance. So is it better to add all test methods in the same Ruby file, or I should put each one in separated code files?
Link between tests and user stories
I have not see these links explicitly stated in the Agile literature I have read. So, I was wondering if this approach was correct: Let a story be defined as “In order to [RESULT], [ROLE] needs to [ACTION]” then
Functional testing before code checkin
I am working on a project with legacy code where it does not have much code coverage. One of the idea to improve that is to enforce a rule that each code check-in must have test, not only test but functional test as well, so that we can verify that the existing code did not break.
We are spending more time implementing functional test than implementing the system itself, is this normal?
Basically, we have three main projects, two of them are web services, and the other is a web application. While I’m satisfied with covering as much as we can of our web services with functional tests (all three projects have their proper unit tests), functional tests for the web application are taking a lot of developer time to get implemented. By a lot I mean two times, or sometimes more, the time that takes to implement the functionality being tested with unit test included.
Difference between functional test and integration test
I am deeply confused the difference. I’ve read so many definitions and they always explain functional test as testing the requirement is satisfied. Well, that’s just rephrasing the name functional test. That doesn’t clarify the difference.
Is this a test smell or is it even worse?
I have recently been looking at some testscripts which looks a bit like
Functional testing and Acceptance testing leading to redundant code
What I know is:
Why is black box called functional testing when it tests also non functional?
This has been bothering me for a while. Security, performance tests etc. are all done typically using the black box approach. But these are nonfunctional,while black box is called functional testing.
Is it okay to test multiple similar files in one functional test
I’ve a functional test using Junit which tests delivery of xml file to an end-point. XML file is sent by client, so I copied it to a test folder, read it from there in my test and do asserts.
Is it okay to test multiple similar files in one functional test
I’ve a functional test using Junit which tests delivery of xml file to an end-point. XML file is sent by client, so I copied it to a test folder, read it from there in my test and do asserts.