3 ms·

Sounds reasonable. (how) do you do testing (unit test and integration tests)?

by e12e 5y ago

XCSme 5y ago
I don't do unit tests (tried it, it was slowing down development too much). I did have integration testing for a while for the core functionality, but in the end that was not helping much either, and after releasing a new version of the app I deleted the tests and (after 2 years) still haven't written new ones, without any bad consequences so far. I deploy a new version to a beta branch, test it myself for a few hours/days (as I do use the app myself daily), then publish it live. Customers gradually upgrade to the new version and if anyone encounters an issue they let me know, and I fix it ASAP, but it almost never happens. Also, the app is pretty complex, so writing tests for every use-case and environment is impossible. I am not a big fan of writing tests when working in a small team (<5 developers). I did work on some pretty big projects that turned out great and very robust, without having written any tests. That being said, if I ever have the time and am bored enough, I will write some integration tests, but mostly for the installation part of the application, not for the usage part.
- tomschlick 5y ago
  > Also, the app is pretty complex, so writing tests for every use-case and environment is impossible. No, you're just using the most expensive / error prone testing methods: doing it manually.
  - XCSme 5y ago
    Maybe my comment was not clear, I do not specifically test the app and all its functionalities. I use the app myself on a daily basis anyway, which acts like a sort-of continuous integration testing program. I use the new version myself for a few days before publishing it, or provide it to some chosen beta testers that use the product anyway.
    - tomschlick 5y ago
      How in the world is that better than automated testing? Rather than being sure that a feature didn't break, you're taking the chance that you or a beta user is going to hit the bug and report it back correctly.
      - XCSme 5y ago
        Rather than spending hours on writing and maintaining tests that are very unlikely to catch any of the future breaking changes, it is indeed better for me than automated testing.

Sounds reasonable. (how) do you do testing (unit test and integration tests)?

by e12e 5y ago

Sounds reasonable. (how) do you do testing (unit test and integration tests)?

I don't do unit tests (tried it, it was slowing down development too much). I did have integration testing for a while for the core functionality, but in the end that was not helping much either, and after releasing a new version of the app I deleted the tests and (after 2 years) still haven't written new ones, without any bad consequences so far. I deploy a new version to a beta branch, test it myself for a few hours/days (as I do use the app myself daily), then publish it live. Customers gradually upgrade to the new version and if anyone encounters an issue they let me know, and I fix it ASAP, but it almost never happens. Also, the app is pretty complex, so writing tests for every use-case and environment is impossible. I am not a big fan of writing tests when working in a small team (<5 developers). I did work on some pretty big projects that turned out great and very robust, without having written any tests. That being said, if I ever have the time and am bored enough, I will write some integration tests, but mostly for the installation part of the application, not for the usage part.

tomschlick 5y ago
> Also, the app is pretty complex, so writing tests for every use-case and environment is impossible. No, you're just using the most expensive / error prone testing methods: doing it manually.
- XCSme 5y ago
  Maybe my comment was not clear, I do not specifically test the app and all its functionalities. I use the app myself on a daily basis anyway, which acts like a sort-of continuous integration testing program. I use the new version myself for a few days before publishing it, or provide it to some chosen beta testers that use the product anyway.
  - tomschlick 5y ago
    How in the world is that better than automated testing? Rather than being sure that a feature didn't break, you're taking the chance that you or a beta user is going to hit the bug and report it back correctly.
    - XCSme 5y ago
      Rather than spending hours on writing and maintaining tests that are very unlikely to catch any of the future breaking changes, it is indeed better for me than automated testing.