• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Liutauras Vilda
  • Knute Snortum
  • Bear Bibeault
Sheriffs:
  • Devaka Cooray
  • Jeanne Boyarsky
  • Junilu Lacar
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • salvin francis
Bartenders:
  • Tim Holloway
  • Piet Souris
  • Frits Walraven

simultanous testing and code commit

 
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hey,

I am facing an issue

I have my server on which the application is under CI by hudson. Also i have fitnesse server running on it. Someone can test the application.

While developers commit their code from remote places.

ISSUE :If a code commit is done and a rebuild is going on......at the same time if some one triying to test it.

Does this break the system.......i am afraid and wanted to know in advance how does the system react to this. It is urgent please.

Any help would be appreciated.

Thanks in advance.
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This sounds like your testers might get their sessions pulled if they're testing while someone triggers a new build.

It's considered a good practice to provide a certain level of stability in an environment with manual testing ongoing. In practice this often means that you need two environments or installations - one used by the CI machinery and another for testing where the latest successful build is installed, say, every night at 3am. This way the test engineers can rest assured that nobody's going to pull the carpet on them during the day.
 
Lasse Koskela
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hmm...

Originally posted by kalyen kumar:
ISSUE :If a code commit is done and a rebuild is going on......at the same time if some one triying to test it.

Does this break the system.......i am afraid and wanted to know in advance how does the system react to this.


I just realized that I may have answered to a different question that was asked. Did you mean that you're concerned 1) whether a new build will screw up ongoing testing, or 2) whether a tester will screw up the new build by clicking on the application while the new build gets installed?

I already answered 1) but if you meant 2) then I'd say it's unlikely but impossible to say for sure without knowing more about the application and its implementation.
 
kalyen kumar
Ranch Hand
Posts: 53
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks for your valuable response.
Also I welcome comments and more information on this

Thanks
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I second Lasse's recommendation: have the fitnesse environment separate from the CI environment. The last step of the CI build could be to automatically update the fitnesse environment with the current version.
 
He puts the "turd" in "saturday". Speaking of which, have you smelled this tiny ad?
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!