641
Marco
Re: Common criteria
  • 2005/1/17 21:31

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


hum,

herko/Dave_L spoke about "the Mozilla Smoketests "

some of you about "Macintosh User Guide Interface is a good example of how creating a common set of expected behaviors helped finnal users"

+ "QA should have a way to make translations and language in general consistent.
Is very confusing if you use two different words in separate module for the same purpose.
Something like a Bank of terms shoul be needed " --> good translation with common words....



642
Marco
Re: Common criteria
  • 2005/1/17 21:27

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


copy paste of jorgebarrero's post


---------
I really think that ergonomy is an issue.

Is not only about if a module works. It is also about if it does what it promises.



643
Marco
Re: Common criteria
  • 2005/1/17 21:25

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


copy paste of danielh2o's posts


------Smoketests format/template, can we start with this...

1 installation

1.1 download
-validate url (as proposed by module developer)
-validate user (if url outside xoops.org, should provide a valid common user for QA download?)
-validate zip file download successful

1.2 preparations
-validate zip file decompression
-validate numbers of decompressed folders / files (e.g. php/sql/language files, as proposed by developer)
-validate README file (or install procedures) existence is a must!
-validate module versions

1.3 install
-validate module files upload successful with required access right
-validate installation procedures (or module upgrade) successful
-validate module existence (ie. admin page)

2 module usage
2.1 admin setting
-block
-group
-preference

2.2 base / configuration data
...
2.3 user functions
...

Should we have a list of 'mandatory' QA items first?

-------------------- another post

Below QA items zoom into my head! Perhaps, some easy for them, some not... depends on module's complexity.

Documentation
-module description (acceptable brief / detail enough)
-installation procedures
-user manual
-technical manual; data dictionary, design specification
-change logs / modification history
-known problems and troubleshoots
-to-do list / future directions

Common practice
-naming standard
-coding standard
-database standard

Quality considerations
-security
-performance
-cache usage / memory leakage
-degree of Object Oriented practice
-reusablity
-scalability
-post support after launch



644
Marco
Re: QA Roadmap
  • 2005/1/17 21:18

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


Dave_L,

can you close some threads, plz, so we start to stop posting everywere and begin to centralize discussion !!!
marco



645
Marco
Re: Certification ? Scalable or One Shot ?
  • 2005/1/17 21:14

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


copy paste of danielh2o's post in https://xoops.org/modules/newbb/viewto ... e=flat&order=ASC&start=10

-----------------------

refer to ROADMAP:
General users maynot familiar with levels:A B C S U and then with certifier:1 2 3
I think "star levels" is much better for user imginations similar to Editor's mark at download.com.
Different "coloured star" or "icons-star" for certifier maybe better too since 1 2 3 showing a sequence or what...

Personally, I think "S" or "U" may have a negative feeling to the module, "No level" is better than that. And I suggest QA team should only start the cert-process after module owner approval (same as @brash), the "star" acts as a scheme/award. They spend much time on their own module, should have the chance to said 'NO' interest to join "star" award (as everyone, except themselve, is a 3rd party to judge)

I wonder if certifier 1 2 3 is a must or not (as foresee QA documents should guide all people to test it). Perhaps, Good point is it will give a sense of belongings and efforts appreciation to QA team/certifier.

PS: MarcoFr, your star ideas is not alone

-----------------

My main experrtice is not related to computers but to Customer Satisfaction. Probably I can help on this issue.

I like the 5 star method. Though I would suggest that each issue be evaluated by itself according to the Module Experience Cycle

1. Startup Information
(Is the name and description enough to know what it does with out installing it?)

2. Instalation Process
(Does it work without any hack, any db trick or so?)

3. Configutation
(Does it start at once with out configuring categories, writing names, or so?)

4. Design
(Is it coded following the XOOPS Standards?)

5. User Interface
(Is it clear for the user how to use the module?)

6. Admin Interface
(Is it clear for the webmaster how to use the interface)

7. Compatibility
(Is it compatible with other modules)

8. Eficiency
(Is it fast and works as expected?)

9. Apparience
(Is it nice, looks good, integrates with your site transparently?)

10. Usefullness
(Does a job that no other module does?)


How do you like this model?

Thanks

Jorge
---------------------------

What do you think about this ????
come on, lets vote !!!
marco



646
Marco
Re: Action List
  • 2005/1/17 21:06

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


Hy !
is everybody sleeeeeeeeeeeeeeping !
I'm ok for action nr 1 !!!!
who else ????
marco



647
Marco
Re: Xoops Download Module V2.1 Beta Released
  • 2005/1/4 20:51

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


here you are
http://www.wf-projects.com

marco



648
Marco
Re: Calendar
  • 2005/1/3 22:52

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


yeh !

Is Everybody still on hollyday ?



649
Marco
Re: QA Smoketests
  • 2004/12/31 14:32

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


just to inform you that I sliced yesterday this thread in several new ones (put all ideas that do not concern Smoketests in news threads grouped by suject)...



650
Marco
Re: Establishing the baseline.
  • 2004/12/30 23:06

  • Marco

  • Home away from home

  • Posts: 1256

  • Since: 2004/3/15


I think we should set a rule for php version, because providers usually take some time to bring their solution at the most accurate version of php.
I know, this delay is decreasing nowadays, but...
... We will have some mistakes in modules with php5, I think, no ?




TopTop
« 1 ... 62 63 64 (65) 66 67 68 ... 71 »



Login

Who's Online

82 user(s) are online (44 user(s) are browsing Support Forums)


Members: 0


Guests: 82


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Aug 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits