11
danielh2o
Re: QA Smoketests
  • 2005/1/6 23:05

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


Glad to join QA Team there are tons of post already... :-O

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?



Quote:

Dave_L wrote:
I think the first, or one of the first items on the agenda is to devise a format/template for module smoketests.

Ackbarr and Herko have suggested that the Mozilla Smoketests may provide a good starting point.

I've also outlined some ideas in this Roadmap.

One way to start is to draft an example smoketest for one of the most common modules. And then we can discuss it, and make some refinements.



12
danielh2o
Re: Image verification process before registration.
  • 2005/1/6 17:40

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


vinit,

Whether your code is same hack stated at this topic?
(or enhancement? or totally new?)

Visual verification during user registration for XOOPS



13
danielh2o
Re: Xoops On Crack?
  • 2005/1/5 11:03

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


Quote:
Anyway, eliminate foreach($_POST...) or extract($_POST) from the codes of core.
This is the 1st step.

Quote:
And newbb2 is also insecure with XSS.

Quote:
And the second step,
Use ticket system for preventing it from CSRF




GIJOE,
Thanks, please tell us more... all security issues you noticed about current XOOPS core and other famous modules, would you mind to share the solutions(if any) to fix too?
At least, all xoopsers should be alerted for all opened-holes...


Xoops Proj.Manager(s) or Dev.Team(s),
Should there be a security guidelines accompany with XOOPS development guidelines(if any)?
I think it is good for setting up a common practice...



14
danielh2o
Re: Xoops On Crack?
  • 2005/1/4 22:48

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


off topic.
hope the planned 2.0.10 still on track!?



15
danielh2o
Re: Homepage (personal editable page) for each user or user group
  • 2005/1/4 22:44

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


Wheeler,
It has cool features!
Will you consider to make a default/sample homepage for user selection? It can be their first big step!

I think general user may know nonething about homepage building by their own.



16
danielh2o
Re: Homepage (personal editable page) for each user or user group
  • 2005/1/3 16:31

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


Good idea to have a user homepages module, I'd like to use it too...



17
danielh2o
Re: mainfile.php changes
  • 2005/1/2 10:23

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


I'd similar accident in mainfile.php when upgrade from 207 -> 2073...

You can solve it without complete reinstallation, just download the patch for 2073->2092 from XOOPS again, unzip, edit mainfile.php to
re-define all those valuable (e.g. XOOPS_ROOT_PATH etc), and then upload your corresponding/damaged file(s) to your server.

ps: if you dont know those values, you may refer to your current damaged mainfile.php for reference, of coz, not refer to your own damaged changes ;-P


Quote:

Asskicker wrote:
database is on. Server was working 15 mins ago. One big mistake i`ve made is:
when i`ve damaged mainfile.php i did manual update from 2.07.3 to 2.09.2 , as mainfile.php exist there also. So i`ve rewritten the mainfile.dist.php and mainfile.php with the rest of the files. I`ve hoped that it will solve the problem.
I cannot go through another reinstallation of xoops, is there something else i can do?



18
danielh2o
Re: [myAlbum-p and piCal] layout problems not caused by theme
  • 2005/1/1 20:57

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


Thanks for guidelines, I will check/try it in details.


Quote:

GIJOE wrote:
It looks just an issue of CSS.

check the margin or padding of your style.css in your theme.



19
danielh2o
Re: Xoops On Crack?
  • 2005/1/1 20:53

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


Frankly, I was not shocked after seeing the demo here. Thanks GIJoe for telling us the sophisticated demo in real.

For new xoopser, like me, you may have similar question mainfile.php secure?

We like xoops, so use it! Visibility to uncovered issue is important, we just want to know what are we using. We're curious about it when we are inbetween know and don't know. However, people tend to wrapped up in the bomb after explosion

Thanks again for all valuable work!
I think all xoopser desire the massaged version 2.0.10 (as proposed here) asap. Should it holds the highest priority in current's core development? any schedule?



20
danielh2o
Re: [myAlbum-p and piCal] layout problems not caused by theme
  • 2004/12/31 21:03

  • danielh2o

  • Just popping in

  • Posts: 47

  • Since: 2004/10/19


GIJoe,
I'd posted here as I cannot register to your XOOPS site.

Would you pls read this topic and give me a helping hand?




TopTop
« 1 (2) 3 4 5 »



Login

Who's Online

258 user(s) are online (180 user(s) are browsing Support Forums)


Members: 0


Guests: 258


more...

Donat-O-Meter

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

Latest GitHub Commits