Downloaded 23 times
![if [ -n "${RUN_NIGHTLY_BUILD}" ];
rspec spec/features --tag "~smoke"](https://image.slidesharecdn.com/tdcsp-otimizandotempodebuild-performancedasutedetestes-160707142516/85/Otimizando-tempo-de-build-performance-da-suite-de-testes-54-320.jpg)
![if [ -n "${RUN_NIGHTLY_BUILD}" ];
rspec spec/features --tag "~smoke"
if [ -z "${RUN_NIGHTLY_BUILD}" ];
rspec spec/features --tag "smoke"](https://image.slidesharecdn.com/tdcsp-otimizandotempodebuild-performancedasutedetestes-160707142516/85/Otimizando-tempo-de-build-performance-da-suite-de-testes-55-320.jpg)
Uploaded byJônatas Paganini
Otimizando tempo de build: performance da suíte de testes
The document discusses optimizing build time and test performance using RSpec in a Ruby application. Key strategies include avoiding unnecessary database interactions and callbacks, utilizing specialized factories, and configuring CircleCI for efficient test execution. The conclusion emphasizes the importance of writing focused tests and benchmarking performance improvements.
More Related Content
Similar to Otimizando tempo de build: performance da suíte de testes
Otimizando tempo de build: performance da suíte de testes
- 1. Optimizing build time Performancerunning tests Jônatas Paganini @jonatasdp
- 2.
- 3.
- 4.
- 5. ~25’ Build time /3 machines
- 6.
- 7.
- 8.
- 9. ~13’ Build time /4 machines
- 10.
- 11.
- 12.
- 13. Avoid callbacks Callbacks canbe lazy and unuseful running all the time
- 14. Model#skip_callback To avoid runthe the hook each factory
- 15.
- 16. after(:create) To run itin a specific factory
- 17.
- 18.
- 19.
- 20.
- 21. Use lazy Associations Associationsnaturally invokes their own factories.
- 22. Avoid factory: forassociations Associations naturally invokes their own factories.
- 23.
- 24.
- 25.
- 26.
- 27. hack sign_in Avoid touchdatabase each login
- 28.
- 29.
- 30. Use stub toavoid inflateassociations
- 33. build Instead ofcreate
- 37. CI Improvements We useCircleCI ● Split specs by context ● Hack postgres.conf ● Postgresql on Memory
- 38.
- 39. CircleCi divide tests bytime NOT context
- 40.
- 41.
- 42.
- 43.
- 44.
- 45.
- 46.
- 47.
- 48. dir=/tmp/postgresql-on-memory mkdir $dir mount -osize=200M,mode=0666 tmpfs $dir
- 49. dir=/tmp/postgresql-on-memory mkdir $dir mount -osize=200M,mode=0666 tmpfs $dir chown postgres:postgres $dir
- 50. dir=/tmp/postgresql-on-memory mkdir $dir mount -osize=200M,mode=0666 tmpfs $dir chown postgres:postgres $dir sudo su - postgres -c '/usr/lib/postgresql/9.4/bin/initdb --encoding=UTF8 --pgdata=$dir
- 51. NEXT LEVEL <what> run<when>
- 52.
- 53.
- 54. if [ -n"${RUN_NIGHTLY_BUILD}" ]; rspec spec/features --tag "~smoke"
- 55. if [ -n"${RUN_NIGHTLY_BUILD}" ]; rspec spec/features --tag "~smoke" if [ -z "${RUN_NIGHTLY_BUILD}" ]; rspec spec/features --tag "smoke"
- 56. http://shipit.resultadosdigitais.com.br/blog ● /ruby-e-rspec-melhorando-a-legibilidade-de-seus-testes/ ● /rspec-performance-tips/ ●/otimizando-testes-factory-girl-e-rspec/
- 57. Conclusion ● Avoid touchdatabase ● Avoid callbacks no sense ● Avoid things you don’t need ● Write specialized factories ● Rate (classify) your test ● Benchmark all isolated steps It’s all about responsibilities
- 58.