FT/TT meeting minutes February 11th 2014

Minutes

General

• Moderator: Steven Sackett
• Secretary: Mario Calderon
• Participants: Mike McKay, Mario Calderon, Suman Ravuri, Victor Perez
• Date / Time: Tuesday, February 11th 2014 / 12:00h - 13:34h GMT
• The meeting closed after 1 hour 34 mins

Agenda

1. Minutes of Previous Meeting
2. Actions taken by RM
3. Actions to be taken
4. Misc
5. Next meeting

Minutes of Previous Meeting

• Previous Meeting Minutes - February 04th 2014

Actions taken by RM

• Merging Susanne's Cost Engine changes, but there were some discrepancies.

Actions to be taken:

• Suman will revert Susanne's Cost Engine changes. She will be asked to reedit her changes with the newest CE version. Then the changes will be merged.

Misc:

• Servers are installed and ready for testing.
• Jenkins server supposedly runs.
• Mike needs the Jenkins process working. He also needs the seed to incorporate the original version of generation of the Sahi IDs.
• Victor will write tests for his features.

Missing:

• Test cases only need to be simple text of what the user would do and what results to expect.
• They would have the following major sections:
  • Setup - what data needs to be in place for the test to work
  • User actions - what does the user do. e.g., Open the order window, create a new POS order, assign it to Joe Block. Move to the line tab, add a new line for Oak tree. Move back to the Order tab. Complete the order.
  • Test: what to test - e.g., Check the order is completed. Check total prices and tax. Check existence of invoice, test existence of shipment. Check zoom across functions.

Community Test:

• Karsten created the Test page under: Release_380LTS_Community_Test.
• In Karsten's opinion there are two possibilities:
  • Document the test results in the test page (ideal: with an integration to Jira) or
  • Use the Jira buglist under ADEMPIERE Jira, with an introduction to Jira's usage in the wiki test page.

Next Meeting:

• Date / Time: Tuesday, February 18th 2014 / 12:00h GMT

Log

Following is the meeting log - time is in GMT -6

Monday, 10 February 2014
[21:45:33] Mario Calderón: http://www.adempiere.com/FT/TT_meeting_minutes_February_04th_2014
[21:46:01] Victor Perez Juarez: Hola Mario
[21:46:09] Yamel Senih: Hola Mario
[21:46:11] Yamel Senih: Hola Victor
[21:46:29] Victor Perez Juarez: hola Yamel
[21:46:49] Mario Calderón: hola Yamel
[21:47:07] Yamel Senih: Como estan?
[21:47:33] Mario Calderón: aqui,preparandolas minutas para mañana
[21:47:49] Mario Calderón: a ver si al fin podemos arrancar a realizar las pruebas
[21:48:13] Yamel Senih: que bueno
[22:56:11] suman ravuri: Hi Victor
[22:56:16] suman ravuri: can we fix the build issue?
[22:57:41] Victor Perez Juarez: Hi Suman
[22:57:48] Victor Perez Juarez: I send a email
[22:57:56] Victor Perez Juarez: do you receipt
Tuesday, 11 February 2014
[06:01:49] Mario Calderón: hello everybody
[06:01:57] suman ravuri: Hi Mario
[06:02:03] suman ravuri: Good Morning
[06:02:37] Michael McKay: Morning.
[06:04:26] Steven Sackett (Adaxa): Hi All..
[06:05:07] Victor Perez Juarez: Hi
[06:05:36] Steven Sackett (Adaxa): are we ready to start?
[06:06:35] suman ravuri: yes
[06:06:59] Steven Sackett (Adaxa): the summary minutes of the previous meeting are....
[06:07:01] Steven Sackett (Adaxa): FT/TT meeting minutes February 04th 2014

Minutes



General

Moderator: Mike McKay (de facto)

Secretary: Mario Calderon

Participants: Mike McKay, Mario Calderon, Suman Ravuri, Colin Rooney

Date / Time: Tuesday, February 04th 2014 / 12:00h - 13:07h GMT

The meeting closed after 1 hour 07 mins

Agenda

Minutes of Previous Meeting

Actions taken by RM

Actions to be taken

Misc

Next meeting

Minutes of Previous Meeting

http://www.adempiere.com/FT/TT_meeting_minutes_January_28th_2014

Actions taken by RM

Actions to be taken

Mario will contact Tobi to support helping with Jirs,Jenkins, etc.

Suman will configure Jenkins, Nexus on Paul Aviles' servers

Misc

Jenkins, Nexus and HG are installed on Paul Aviles' servers.

demo1.adempiere.us

http://nexus.adempiere.us/index.html#welcome

http://hg.adempiere.us/

Steps to get the instances running:

Gain access to the server (Suman and his team)

Configure Jenkins, Nexus and HG to be able to nightly load changes, build the code and update the database. (Suman and team)

Configure Sahi (Mike - in parallel with tests)

Configure a method to track test progress - keep in simple so we can register test volunteers, capture bugs and fixes as we go. (Need to setup Jira and mail list - need a test team lead (Mike - may need help from Tobi admin on Jira)

Communicate with the community on the process - whats been changed, what needs to be tested, how to communicate results, where to sign-up to help etc... (Mike and others)

Kick-off the tests (Target Feb)

Test cycles (all)

Prepare the official release once the testing is complete - final quality checks and repository clean up - Victor did this last time. (Suman/Victor following acceptance of tests)

Launch the release (Mid April?). Start planning for the next one.

Next meeting

Date / Time: Tuesday, February 11th 2014 / 12:00h GMT
[06:07:25] Mario Calderón: same roles?
[06:07:56] Steven Sackett (Adaxa): unless other candidates want to put their hands up?
[06:08:23] Steven Sackett (Adaxa): anyone want to be moderator? please!
[06:09:18] Steven Sackett (Adaxa): what tasks were scheduled for the week and what has been achieved?
[06:09:43] Steven Sackett (Adaxa): Suman, can you give us an update?
[06:10:37] suman ravuri: Steve, we have an issue with build
[06:11:00] suman ravuri: struggling solve this with existing tools I have
[06:11:38] Steven Sackett (Adaxa): what is nature of problem?
[06:11:43] suman ravuri: Documented in https://adempiere.atlassian.net/browse/ADEMPIERE-250
[06:12:03] suman ravuri: issue beacuse of two repositories
[06:12:54] Victor Perez Juarez: Of merge cost was incorrect
[06:13:27] Mario Calderón: now solved?
[06:13:37] suman ravuri: not yet
[06:13:39] Victor Perez Juarez: It cause duplicate classes
[06:14:11] suman ravuri: we had long conversation with Victor and decided to take help from Susanne
[06:15:14] suman ravuri: Mike, did you get a chance to look at jira issue
[06:15:54] Victor Perez Juarez: Susanne's changes are of a Cost engine versión old
[06:16:10] Michael McKay: Sorry - which issue - the one above or settingup test cases?
[06:16:22] suman ravuri: [5:42:41 PM] suman ravuri: https://adempiere.atlassian.net/browse/ADEMPIERE-250



<<< 
[06:16:56] Michael McKay: Just read it.  I haven't looked at the code yet.
[06:17:32] Victor Perez Juarez: Suman tried use of versión of Sussanne but not is right
[06:18:38] suman ravuri:  I integrared the code what ever I received, last time I received on December 3rd
[06:18:54] suman ravuri: I am yet to receive another update
[06:19:05] Mario Calderón: so susanne will be contacted and issue solved
[06:19:08] suman ravuri: I am fine to integrate quickly with latest code
[06:19:29] suman ravuri: but not able to solve multi repo issue
[06:19:38] Victor Perez Juarez: Only should take of changes , I know that susanne have comenta mark in yor code , so that merge should be manuality compare file by file
[06:20:35] Mario Calderón: Ok
[06:21:27] Steven Sackett (Adaxa): Hi Victor can you explain a little more
[06:22:44] Victor Perez Juarez: Then suman copy clases in path that susanne had but it change in cost engine branch
[06:23:03] Victor Perez Juarez: For example of package
[06:24:35] Victor Perez Juarez: In cost engine branch i make of necessary change to integrate with 380 branch and it was ok
[06:24:35] Steven Sackett (Adaxa): so what needs to be the next steps?
[06:25:04] Mario Calderón: As victor told me, susanne made her changes on old versions of costing engine files, and  the code was deployed as a different package.
[06:25:31] Mario Calderón: But now this is known, and how to be tackled
[06:26:00] Victor Perez Juarez: i use org.adempiere.engine vs org.adempiere.engines
[06:26:34] Victor Perez Juarez: And i remove this from libero and move to core
[06:26:57] Mario Calderón: Best would be that victor talks to susanne and they construct the files to be merged. Then suman cqn do the merge
[06:27:23] Victor Perez Juarez: But as Sussanne change are old suman replicate old structure
[06:28:30] suman ravuri: Here is the plan I can think of
[06:28:53] suman ravuri: 1.Share latest costing changes to us, we will integrate
[06:29:32] suman ravuri: 2. For sub repo issue, we will revert the changes and Victor would help us to fix this
[06:29:34] Victor Perez Juarez: Suban and me think that is more easy may be that susanne include your changes form a repisitory update
[06:29:57] Victor Perez Juarez: She know that change introduce
[06:30:32] suman ravuri: can Susanne fix sub repo changes?
[06:30:36] Mario Calderón: Ok
[06:31:08] suman ravuri: I mean costing depends of manufacturing which is in altogether different repo
[06:31:36] Mario Calderón: I will tell her to contact you both after this meeting
[06:31:42] Victor Perez Juarez: Suman you should revert útil 2110 revisión
[06:31:57] Mario Calderón: Steven, can we move on?
[06:32:13] Steven Sackett (Adaxa): sure
[06:32:26] Victor Perez Juarez: Because of repository is ok in 2109
[06:32:35] Victor Perez Juarez: I sent a email
[06:32:51] Steven Sackett (Adaxa): Test servers?
[06:33:10] Steven Sackett (Adaxa): available yet for people to start testing?
[06:33:56] Victor Perez Juarez: Yes Paul finish
[06:34:02] suman ravuri: the issue we discussed is show stopper to come up with test instances
[06:34:08] Victor Perez Juarez: Oracle and pg
[06:34:39] Victor Perez Juarez: Only are of code to finish install
[06:35:43] Steven Sackett (Adaxa): Victor, how do I access a test instance?
[06:35:53] Yamel Senih: Hi All
[06:36:31] Mario Calderón: Is jenkins configured and Does jenkins run?
[06:36:54] Mario Calderón: Hi yamel, nice to meet you here
[06:36:58] Victor Perez Juarez: When code is ready Paul execute a script that generate new dB seed
[06:37:20] Victor Perez Juarez: And deployment adempiere
[06:37:36] Steven Sackett (Adaxa): so no test instance till the code problem Suman is talking about is fixed?
[06:37:36] Mario Calderón: Mike sent an email about sahi also....
[06:38:00] Victor Perez Juarez: I made of change necessary to release a new versión and commit
[06:38:40] Victor Perez Juarez: But was here when detect issue with merge
[06:38:58] Michael McKay: I'm ready to start but need the jenkins process working.  Also need the seed to incorporate the original version of generation of the sahi IDs.
[06:39:47] Michael McKay: Also haven't heard from Tobi on Jira and using the test cases there.
[06:39:56] Victor Perez Juarez: Yes Mike
[06:40:10] Victor Perez Juarez: I have this changes and other
[06:40:21] Victor Perez Juarez: To test
[06:40:58] Victor Perez Juarez: In social with timeout of a test
[06:41:16] Victor Perez Juarez: It can get timeout
[06:41:43] Mario Calderón: I wrote -yesterday very, very late - karsten if he could wrap up what has been done and what is missin about the wiki test page
[06:41:52] Victor Perez Juarez: But i am wait that code is ok to integrate this changes
[06:42:14] Mario Calderón: When he answers, i will inform you
[06:43:01] Victor Perez Juarez: I know Paul have of jenkins server ready
[06:43:13] Victor Perez Juarez: You can ask he
[06:43:25] Michael McKay: I can deal with timeouts once the instance is up and running.  Other things I need are test cases for the new modules and features.
[06:43:50] Michael McKay: I can help build the automated tests around these.
[06:43:59] Victor Perez Juarez: Exacly
[06:45:15] Michael McKay: I have or can generate the tests for everything I've committed.  Can I ask everyone else to send me the test cases for their code?  It will speed things up a lot.
[06:47:58] Mario Calderón: Ok
[06:48:25] Mario Calderón: So, what is missing now?
[06:50:58] Michael McKay: Test cases only need to be simple text of what the user would do and what results to expect.  They would have the following major sections:

* Setup - what data needs to be in place for the test to work

* User actions - what does the user do.  ie. Open the order window, create a new POS order, assign it to Joe Block.  Move to the line tab, add a new line for Oak tree.  Move back to the Order tab.  Complete the order.

* Test: what to test - ie. Check the order is completed.  Check total prices and tax.  Check existence of invoice, test existence of shipment. Check zoom across functions.
[06:51:55] Steven Sackett (Adaxa): @Mike, thanks for making that clear for me..
[06:52:42] suman ravuri: @Mike, we prepared test documents for most of the features we integrated
[06:53:12] suman ravuri: We covered all basic scenarios
[06:53:16] Michael McKay: Are they in Jira?
[06:53:19] suman ravuri: yes
[06:53:24] suman ravuri: they are in Jira
[06:54:08] Michael McKay: Good.  I'll have a look and try to develop SAHI tests around them.
[06:55:25] Steven Sackett (Adaxa): the setup/user actions/test scenario for something like Mfg Light wlll be quite extensive.. I s that what is expected?  does anything exist yet?
[06:55:40] Victor Perez Juarez: Mike exist this script in wiki
[06:55:44] Steven Sackett (Adaxa): @Suman?
[06:56:02] Victor Perez Juarez: Let me send URL
[06:56:07] Steven Sackett (Adaxa): we did not write any test cases like that
[06:56:35] Mario Calderón: SOrry for coming back to this issue, but Iwant to make sure we agree on this. Wrapping up the costing engine issue, summan will revert all changes, merges, etc so the code is again ready to take up susanne's changes. Victor and susanne will work together so her changes are quicly implemented and readey to be merged.
[06:57:05] suman ravuri: For ML I need  to verify once, but for other features we have detailed documents like create user, add sales order et...
[06:57:50] Michael McKay: @Victor - for the main functional tests, yes.  But not for the new features and modules.
[06:58:53] Steven Sackett (Adaxa): Mario's question seems to be the most critical thing, can Suman and Victor confirm their agreement to get this work done. I assume Mario will ask Susanne soon..
[06:59:05] suman ravuri: Yes I will revert the changes
[06:59:14] suman ravuri: and let Victor and team know
[06:59:39] Steven Sackett (Adaxa): what is the timeframe to get this finished please..
[07:00:19] suman ravuri: By 11AM IST tomorrow, I will revert
[07:00:53] Steven Sackett (Adaxa): thanks .. @Victor, what time might you need for extra work?
[07:04:24] Steven Sackett (Adaxa): anyone have more to add?
[07:05:41] Steven Sackett (Adaxa): thanks .. I assume we meet next week, hopefully with the above tasks completed.. bye
[07:07:09] Mario Calderón: The test page
[07:08:11] Michael McKay: Before we write too much - I'd like to get Jira setup to coordinate the test activity.
[07:08:30] Michael McKay: But - I can help with the test page if Karsten doesn't have time.
[07:08:47] Mario Calderón: Here are missing the integration with jira, the easy explanations to use it
[07:09:02] Mario Calderón: Ok....
[07:09:12] Michael McKay: Have to leave for a few minutes ...
[07:10:36] Mario Calderón: Anything else?
[07:16:15] Mario Calderón: If not, please write here comments etc. I will consider them in the minutes
[07:16:50] Victor Perez Juarez: not fro me Mario
[07:17:22] Mario Calderón: Suman?
[07:19:17] Victor Perez Juarez: Mike
[07:19:29] Victor Perez Juarez: here are the test page
[07:19:32] Victor Perez Juarez: http://www.adempiere.com/Functional_Tests
[07:19:42] Victor Perez Juarez: we need complete for new functionality
[07:22:41] Michael McKay: Yes.  In the sahi tests, I've been using that list to generate the main functional tests.  There is lots to do and I wouldn't consider attempting all of it for the 380 release - just the relevant changes.  I'll keep adding to the main functional tests as we go.
[07:24:14] Victor Perez Juarez: but is important have
[07:24:50] Victor Perez Juarez: this way can have regression test
[07:25:10] Victor Perez Juarez: and know if some was broke
[07:26:50] Michael McKay: Agreed -  it is just a question of time/resources to cover the whole list.  Is there a way to focus the effort on critical sections?
[07:28:03] Michael McKay: For those interested in helping out with the sahi test development, I've added more details here: http://www.adempiere.com/ADempiere_Testing_with_Sahi



Its not finished yet. When it is, it should be clear how to go about developing an automated test.
[07:28:09] Victor Perez Juarez: I will write for my new features
[07:28:14] Michael McKay: Thanks.
[07:28:18] Victor Perez Juarez: other should be same
[07:29:08] Mario Calderón: ok
[07:29:15] Mario Calderón: are we finished?
[07:29:31] Victor Perez Juarez: yes from me
[07:29:49] Michael McKay: Nothing else from me.  Thanks.
[07:34:12] Mario Calderón: Bye
[08:58:29] Mario Calderón: hi, here Karsten's report about test page: 



Karsten created the Test page under: http://www.adempiere.com/Release_380LTS_Community_Test .



In Karsten's opinion there are two possibilities: 

1.- to document in this page the test results in the test page (ideal: with an integration to Jira)or 



2.- to use the Jira buglist under https://adempiere.atlassian.net/issues/?jql=project%20%3D%20ADEMPIERE , with an introduction to Jira's usage in the wiki test page.