Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

How can we keep our web application up-to-date with the rapid release schedule?

  • 3 Mbohovái
  • 1 oguereko ko apañuái
  • 3 Hecha
  • Mbohovái ipaháva knorretje

more options

Hi,

We are currently offering a web based b2b application. But with the rapid release schedule that's been recently introduced, we are having trouble testing our application for every new version of firefox. It's a very time consuming job completely checking the application.

Is there any way we can know if a new version of Firefox needs actual testing, or do we have to test each new release?

Regards,

Arjan van der Hulst

Hi, We are currently offering a web based b2b application. But with the rapid release schedule that's been recently introduced, we are having trouble testing our application for every new version of firefox. It's a very time consuming job completely checking the application. Is there any way we can know if a new version of Firefox needs actual testing, or do we have to test each new release? Regards, Arjan van der Hulst

Opaite Mbohovái (3)

more options

You can read on Mozilla Developer Network (MDN) what's going to change in the next version of Firefox. These articles are called "Firefox <number> for developers". Maybe you can use that list to decide how mutch testing you are actually going to need. Also, if you are always coding against the current web-standards, that's also going to reduce the chances of something breaking your application.

https://developer.mozilla.org/en/Firefox_7_for_developers

more options

Thanks, will look into that :)

more options

I found this article from Jesse Ruderman that may be interesting to you. It has some good ideas for testing and requirements.

improving-intranet-compatibility