The first part I must state is that this is not because certain tests must run before others. We have to run full regressions every week, that generates a singular report and not lots of smaller reports (I asked and management doesn't want this), 11k scenarios and we tag each scenario with the release they are associated with. We would love to be able to run the scenarios in specific orders depending on what occurred during the release so that we aren't wasting time waiting for the 100th from the last test to fail only to have to start from scratch again, or at the very least run certain files first.
I know there is the solution of just renaming the folders/files each release, which is what I am doing, but it is extremely tedious and I would like to just change something in our Java runner.
There are similar questions from years ago, so I am hoping some hack or feature has been added that I just can't seem to find.
Searching for examples of Cron usage and Cron parsing tools for cron's syntax, I see some tools with 5 input places and some with 6 (the sixth being for a seconds field). Furthermore, I see some flavors which support ? character as a valid input while other variants do not.
Does cron have an authoritative standards document for cron syntax? (E.g. an RFC or an ISO document). Or is cron just a loose collection of similar tools each with their own syntax rules?
I am working on an existing CMS. We were thinking if it would be usefull to work with a cronjob. When thinking on this, we could only think on updating the search index for the cronjob, so we have no idea if we should add the cronjob to our CMS or not ...
What do you think?
Are you asking whether or not it would be useful, I think that it absolutely can be for certain tasks.
Having done some Drupal development, I know that it tends to use cronjobs for aggregating feeds, caching pages, creating logs and a whole host of other things.
see http://drupal.org/cron for a more in-depth example/explanation.
If you have a valid need to perform some batch type of operations off of your main server then a cronjob makes perfect sense, but I wouldn't start adding them just for the sake of having them.
Instead of using cron to execute your scripts directly, you could implement a scheduler in whatever language you're using and just have cron give it a heartbeat. I would do this if I had multiple tasks to schedule for my site and didn't want to scatter logic everywhere.
Something like this spec: http://code.google.com/p/djangotaskscheduler/wiki/OriginalRequirements
If it is no customer requirement just leave it. It only adds complexity and has to be testet without adding any real value.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
We are starting to adopt agile in a project we are about to begin.
Although I am not actually involved in the development of this project, I am involved in the stand up meetings.
Is it acceptable to say how you are learning a new technology (eg C# 4.0) as one of your tasks, alongside the actual deliverables?
My task is constant everyday so it is embarassing to say how I am doing the same thing (which is not a fun task - more admin type) while the other team members are doing C#/ASP.NET - the fun stuff. This obviously dents my morale.
How should I approach these meetings?
Thanks
Is it acceptable to say how you are
learning a new technology (eg C# 4.0)
as one of your tasks, alongside the
actual deliverables?
Learning time is legitimate, and if the company sees it that way you can make it a task.
Full disclosure: although the company I work for sees learning as a part of the process of software development, I don't actually put individual learning tasks into my weekly reports; I just build it in as a part of the larger development task.
My task is constant everyday so it is
embarassing to say how I am doing the
same thing (which is not a fun task -
more admin type) while the other team
members are doing C#/ASP.NET - the fun
stuff. This obviously dents my morale
Where I work the people that have ongoing "areas of achievement" list the individual tasks they achieved when we meet each week. Some of these tasks can be quite mundane, such as "I went to this meeting," or "I ran this script that took 2 hours," or even, "I read this chapter of that book because I needed to know how to do this." Our company understands that this is the nature of the work. You shouldn't be embarrassed about this.
Full disclosure: I break my "areas of achievement" into smaller goals that can be completed in roughly a week's time, so that each week I can say that I completed something.
I'd try to embrace the three questions:
What did I do yesterday? (Did you
learn about some of the dynamic new
features of C#?)
What are you going
to do today? (Do something with what
you have learnt that challenges you)
What is impeding you? (If you lack a
skill look to the senior guys to
help teach you.)
Kindness,
Dan
Suggest that you are a "chicken" in the process, which is an agile term for being an observer to the meeting but not a participant. http://www.agilejedi.com/chickenandpig
Since you consider your present task 'embaressing', I am assuming that you want some more development responsibility.
In my opinion is the stand up is probably a good time to ask for this.
I suggest that you say something passive like: before the next standup I will try to put what I have learned thus far in C# 4.0 to good use within some area of the project.
You in short order, you will be given something to do... then instead of having nothing to say during the stand ups, you will be too tired to go to them.
be careful what you wish for... because some day, you might get it.
As a junior, you're expected to learn. So, unless you feel admitting to learning would imply you're not doing your other tasks, I say go for it.
You can still report what you learned yesterday, what you plan to learn / try out today, and if you have any blockers that are preventing you from learning.
You will not spend the whole career as "Junior" (and everyone too). How do the team know that you can do higher responsibility? of course by showing that you're capable of. As it's Agile meeting, I believe everyone will have chance to show his idea.
Do your best to answer questions and show your "out of the box" idea to the team.
One day once they think that you can handle higher responsibility, you will out from your current position to more challenging works.
Learning/knowing something doesn't show that you can use it. There are some way to let the team know about your C# 4.0, by talk about it at lunch, writing on your blog then let your team know, write some tool for your daily tasks, etc.
Not only on the meeting :-)
Good luck!
Where I work, we do have people that will say in the stand up that their day will be spent on non-project work as the stand up is for a specific project that almost everyone speaking in the stand-up has a part.
If you repeat the same task a few days in a row in stand-up, you may be asked why you are taking so long on a card, if you have enough resources, etc. as there may be some thought that you are off on a tangent or spike.
In my university days I came across a Java app in one of my courses. You basically modeled your threads (any actions they perform etc.) in a simple language. It would draw a diagram and identify and issues with your threading. Does anyone know what this app is called? I have tried for the last 30 mins on Google but can't find anything.
I guess you mean "Thread State Diagrams". Maybe something like this?
http://support.objecteering.com/objecteering6.1/help/us/objecteering_uml_modeler/diagrams/state_diagrams.htm